Bug #19170 2013-10-30 11:13
kashej
command line build order
The order in which command-line options are assembled is not right.
Project-specific options are included into the command line first and therefore cannot override options specified in general settings. For example: if I have a general setting -Wall (show all warnings), I cannot suppress a specific warning by specifying -Wno-float-equal in project build options, because command line would look like that:
g++.exe -Wno-float-equal -Wall program.cpp
and -Wall overrides project's settings.
I propose the following order of command-line assembly:
1) options from Settings - Compiler - Compiler flags;
2) options from Settings - Compiler - Other options;
3) options from Project build options - Compiler - Compiler flags;
4) options from Project build options - Compiler - Other options;
- Category
- Application::WrongBehaviour
- Group
- Platform:Windows
- Status
- Open
- Close date
- Assigned to
History
So, you mean the Global compiler setting should be put first, and later the Compiler options for the current project?
Exactly. So generic, apply-to-all settings can be overridden by project's settings.