Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
Alpha:
--- Quote from: MortenMacFly on June 29, 2012, 07:14:09 am ---Another (simpler) option is to have the compiler class hold the autodetector and provide a single method
[...]
--- End quote ---
OK, I will experiment with this. Would you happen to know if this technique is used elsewhere in Code::Blocks, so that I could examine it?
I believe I will be busy for a few days, so I am not certain when my next patch will come.
MortenMacFly:
--- Quote from: Alpha on June 30, 2012, 04:12:42 am ---Would you happen to know if this technique is used elsewhere in Code::Blocks, so that I could examine it?
--- End quote ---
Mmmmh... not to my knowledge. It would be a tooling class. So it its easier for you to derive from - just go that way. In the end from an interface point of view its the same.
--- Quote from: Alpha on June 30, 2012, 04:12:42 am ---I believe I will be busy for a few days, so I am not certain when my next patch will come.
--- End quote ---
No üroblem, leaves more time for me to test. BTW: already now I have used it a lot w/o issues. Just the patch needs tweaks to compile w/o PCH and on wx 2.9.x.
Alpha:
--- Quote from: Alpha on June 30, 2012, 04:12:42 am ---I believe I will be busy for a few days, so I am not certain when my next patch will come.
--- End quote ---
... maybe that was a bit more than a few days...
I think I have a working extension to the <if> statements now. Does anyone have specific example flags that should be hidden if the compiler is detected as a certain version? (Or a link to where I can find a listing of flags added by compiler version.)
Alpha:
--- Quote from: MortenMacFly on June 27, 2012, 08:52:53 am ---- compileroptionsdlg: The global var "menuOption" should become a class member var "m_MenuOption"
--- End quote ---
By the way, this change causes the passing on of the event id to mysteriously fail (no errors are raised, and according to gdb, m_MenuOption reverts -1 when OnFlagsPopupClick() returns).
However, it does work if I make it a static class member. Would this still be the preferred method?
MortenMacFly:
--- Quote from: Alpha on July 10, 2012, 03:34:16 am ---Does anyone have specific example flags that should be hidden if the compiler is detected as a certain version?
--- End quote ---
Certainly the platform flags usually need attention. Also, -std=c++0x and -std=c++11 and some warnings (like -Weffc++) have not always been available.
The GCC webpage will always tell you what's new, like here:
http://gcc.gnu.org/gcc-4.3/changes.html
...under the section "IA-32/x86-64" you'll see that i.e. -mtune=core2 has been added in this version (4.3).
From my point of view we should consider the last 3.x.x version in contrast to 4.0.x and then 4.5, 4.6 and 4.7 which should cover the main up-to-date compilers. Maybe not all of the flags, but the ones that seem important. If its configurable in the end we can do it step by step anyways...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version