Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
MortenMacFly:
--- Quote from: Alpha on June 22, 2012, 04:44:46 pm ---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?
--- End quote ---
One thing I could think of is an if-statement to check for a compiler version... not sure how to handle this at startp w/o running the compiler though.
Alpha:
Is it correct for me to assume that the GCC regexes (located in compilerMINGW.cpp) are applicable to all supported (C/C++) GCC variants (ARM, TriCore, ...)?
MortenMacFly:
--- Quote from: Alpha on June 24, 2012, 01:53:20 pm ---Is it correct for me to assume that the GCC regexes (located in compilerMINGW.cpp) are applicable to all supported (C/C++) GCC variants (ARM, TriCore, ...)?
--- End quote ---
I think it isn't wrong in a first place, but to be sure you'd have to ask the compiler guys developing these. I never worked with ARM/TriCore compilers.
However, from what I see they might override some of the options.
MortenMacFly:
OK, here comes some more from the testing front:
First of all: Also the new patch works great, I didn't have to change a lot (just the very minor stuff I was already referring to).
* The flags dialog is well-hidden I'd say, so I suggest to add a (red) note below the compiler flags to inform the user that this is actually adaptable.
* The flags dialog should be resizable (I did this in my local copy already)
* I don't know if it is really needed to allow toggling the additional flags (for the checks) with this ">" button. Instead, I'd prefer to have them always visible below the major flags so see the full picture. The reason is that you look what's hidden there anyways... ;-)
What didn't work for me is when I add a flag with a different (new) category, the new category does not appear in the "Categories" choicebox of the compiler options, although its present.
The log-term goal should probably be to have the compiler setup (not the project's compiler options setup) unified in a single dialog, including the advanced stuff, reachable only from the compiler settings dialog. For now, you can change the compiler flags even in the project build options, which is kind of mis-leading I'd say. Also, I don't like having the different options scattered in so many dialogs with different access points. But in the end that's "fine-tuning" (maybe not on your list) and I believe we can even re-use the UI resources already created by then.
MortenMacFly:
--- Quote from: MortenMacFly on June 26, 2012, 08:57:17 am ---What didn't work for me is when I add a flag with a different (new) category, the new category does not appear in the "Categories" choicebox of the compiler options, although its present.
--- End quote ---
Oh well, now I figured out something else: Looking at the modified compiler XML file I realised that if you change a flag the <if> <else> sections are gone, meaning, that the options are no longer cross-platform. Also, the "Common" options are integrated and no longer linked. Is this by design?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version