Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
Alpha:
I use a (slightly old) self compiled version of Clang from their trunk. The Clang compiler I wrote has only been lightly tested (much if it is written based on pure documentation), so beware of errors.
--- Quote from: MortenMacFly on July 19, 2012, 08:15:45 am ---Do you have an easy way/tool to convert/add this?
--- End quote ---
The absolute easiest way is to register it in compilergcc.cpp as a normal compiler, then (build and) launch Code::Blocks, open the compiler settings, create (and delete) a new flag for the compiler (to make it think it has changed), and click OK. This will generate a fully usable file in your user data folder.
However, I usually uses my ListToolbox plugin, because with it, I can make the output look much nicer. (Using ListToolbox takes about equivalent effort as formatting one of each type of entry because of the way it chains commands.)
However (2), you could just apply this patch ;) (it also contains a fix for the loading of copied compilers whose flags have been changed, and slightly more along the lines of auto-detection routines for pure XML compilers).
--- Quote from: MortenMacFly on July 18, 2012, 08:04:51 am ---Did you try what happens if you create a copy of a compiler? Dos that still work?
--- End quote ---
It does work except that copied compilers do not load user customized sets of compiler flags; this fixes it.
MortenMacFly:
--- Quote from: Alpha on July 19, 2012, 05:43:44 pm ---It does work except that copied compilers do not load user customized sets of compiler flags; this fixes it.
--- End quote ---
So... to summarise: It works pretty well and I don't see major drawbacks. It only needs testing on Linux.
What do you think is missing?
Alpha:
I would like to finish registry support and a couple other tweaks for pure XML compilers. I also want to allow compilers to specify a 'weight' - which would be used to decide what order to display them in. There are also some compilers with relatively uncomplicated auto-detect that I think can be swapped for pure XML.
From my perspective: Linux testing, and auto-detect testing (after I rewrite to XML the compilers I can).
Jenna:
--- Quote from: Alpha on July 20, 2012, 11:31:25 pm ---From my perspective: Linux testing,
--- End quote ---
I just committed fixes to the linux project-file and the automake-system.
It's compilable and seems to work:
I used C::B compiled with automake to compile C::B with C::B and run it from inside C::B.
..., but I did no deeper testing.
Alpha:
This patch completes the remaining features I currently have planned:
* Compiler weight
* Dynamic tooltip for auto-detect compilers dialog
* More XML compiler auto-detection routines
* Converted some compilers (the easy ones) to pure XML (to anyone who uses any of the following: please test to ensure auto-detection works at least as good as before)
* Digital Mars Compiler
* LLVM D Compiler
* GNU GCC Compiler for MSP430
* PGI Fortran Compiler
* GNU GCC Compiler for PowerPC
* Small Device C Compiler
* Tiny C Compiler
* GNU GCC Compiler for TriCore
I would recommend that testers delete their current default.conf (or launch Code::Blocks with a new profile) because this branch does make a few (minor) changes to how the compilers save (which may, or may not interfere).
--- Quote from: jens on July 20, 2012, 11:51:15 pm ---I just committed fixes to the linux project-file and the automake-system.
--- End quote ---
Sorry, I think this brakes the build system again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version