2.) I think later on we can/should transfer the regexes and advanced compiler options to the XML file, too. For this, it needs an interface to the configmanager.
What are these other advanced compiler options? I think the XML files currently contain all options except for the regexes.
files currently only contain settings that could be losslessly transferred from C++. Looking at the various settings each compiler contains, it appears that regexes are the only remaining items that fit this requirement; the next patch will support these in the options files.
The other main component of a compiler is auto-detect. I will be creating some (limited) functionality of this in compiler_
files (files I am working on for dynamically detected pure XML compilers).
...I just saw: Did you realise SVN revision 8060? Is this already integrated?
Yes (and it was very fast to do; adding this new flag to options_common_warnings.xml
put it in the whole GNU family).
About message boxes/error handling, what I have written so far mostly makes the (incorrect) assumption that it will only be fed properly formed files. Eventually something more robust will need to be added...
- Warning messages if multiple compiler options are unwise to use together (but still legal)
- Automatic disabling of conflicting compiler options (for example, enabling debug symbols automatically disables strip)
(I am no compiler expert, so I only added these interactions where they were obvious. Feel free to let me know of any flag interactions I have missed/messed up.)
Question: The only condition that <if></if>
blocks currently recognize is platform
- are there any other conditions that would be made use of during the loading of a compiler?