[Bug 57117] New: Compiler flags settings are forgotten

[Alexander Dymo]

> From main menu with a C++ project, do the following:
>
> Project --> Project Options --> Configure Options --> C++
> Add some custom options such as -I/usr/qt/3/include
> Click on the [...] on the Compiler Flags line.
> Modify some settings (e.g. add a warning)
>
> Expected result:
> Custom option such as -I/usr/qt/3/include would stay in the textbox.  The
> additional settings added by selecting them in the [...] options would be
> ADDED TO the list (or removed, as appropriate).
>
> Alternate expected result:
> Gideon would warn me that it was about to overwrite the settings I had
> configured.  This would be a nasty workaround but better than the current
> behaviour.
>
> Actual result:
> Custom options I have previously entered are removed entirely.

Compiler flags input fields are not the good places for include paths,
so I've implemented two input fields in Configure Options -> General:
C/C++ Preprocessor flags (for -I<path>)
Linker flags (for -L<path>)
BTW, linker and include settings are available in automake
manager for subproject and target options too.

Nevertheless, I've corrected the behaviour of compiler options
dialod. It will not touch those user-defined settings that it can not
recognize.

Please somebody close this bug.

-- 
Alexander Dymo
Ukrainian State Maritime Technical University, IT Department