Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
killerbot:
I had a nightly ready, but during testing on linux I found a showstopper, the 2 latest compiler option/directives are still missing.
They are present in some (did not check all of them) gcc derivatives/ports (like gnu arm), but are missing in the main gcc.
I am talking about :
- std=c++11
- Wzero-as-null-pointer-constant
How can we be sure not other options have disappeared ?
Next to the issue, I have a question what advice to we want to give wrt "default.conf",
We will ask the user to backup, but then what, do they need to remove something out of it (the compiler section, but for sure not the user sets) ?
EDIT : can the compiler detection at startup be explained, it made no sense to me.
Pre-suported compilers (which were absent) were now user defined ??
Other were grey-ed out.
Some where red ?
I don't get it, for ther majority of them I would have expected the same thing.
Jenna:
My build is not the newest one (I have 8218), and the two options you have mentioned are there.
I start the xml-branch with an own personality and do not use the default.conf of trunk, maybe that's the reason.
Alpha:
--- Quote from: killerbot on August 28, 2012, 09:16:39 pm ---I had a nightly ready, but during testing on linux I found a showstopper, the 2 latest compiler option/directives are still missing.
--- End quote ---
In share\CodeBlocks\compilers (user, not global), XML files will be saved for any compilers to which flags have been changed/added/removed. It is possible options_gcc.xml was generated during a previous test before the version detection was fixed. These files are loaded preferentially, so either deleting it manually, or resetting the compiler should resolve the problem.
--- Quote from: killerbot on August 28, 2012, 09:16:39 pm ---EDIT : can the compiler detection at startup be explained, it made no sense to me.
--- End quote ---
The ones labeled "user defined" mean that they were not detected, but the master path loaded from default.conf is different than that given by auto-detection (this happens either when the user has set their own path, or when auto-detection has changed defaults).
Grey-ed out means the compiler was simply not detected (but the master path loaded from default.conf is the same as auto-detection).
Red means that the master path was empty before auto-detection began. The detection dialog will only be shown if at least one compiler has an empty path. The purpose is to alert the user that the highlighted compiler(s) are invalid and (may) require attention. (I have another idea to more accurately mark this - currently new compilers are incorrectly marked red as well; I should have a small patch for this soon.)
Alpha:
--- Quote from: killerbot on August 28, 2012, 09:16:39 pm ---We will ask the user to backup, but then what, do they need to remove something out of it (the compiler section, but for sure not the user sets) ?
--- End quote ---
In my opinion, it should be fine to continue working with the same (unmodified) default.conf (of course, it still should be backed up just in case).
MortenMacFly:
--- Quote from: jens on August 28, 2012, 10:12:53 pm ---My build is not the newest one (I have 8218), and the two options you have mentioned are there.
--- End quote ---
For me, too - both options are there.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version