Developer forums (C::B DEVELOPMENT STRICTLY!) > Compiler Framework Redesign
XML based compilers
MortenMacFly:
--- Quote from: jens on August 03, 2012, 11:26:32 am ---The checkbox to allow non-platform compilers needs a restart to have an effect.
--- End quote ---
Maybe to clarify, where this comes from: I recently discussed with Alpha the following:
--- Quote from: MortenMacFly ---Something else in between: I read this:
http://www.orbiterwiki.org/wiki/Free_Compiler_Setup_Under_Linux
And I had an idea: Whats missing for the compiler but would really be useful for cross compiling is that you could setup via Config/API (!) if a compiler is attached/active under the current platform. [...]
--- End quote ---
But yes, the restart should be clarified.
Edit: Done.
Alpha:
--- Quote from: MortenMacFly on August 03, 2012, 06:49:26 am ---Didn't you mean to replace "_" (underscore) with "" (empty)? Here, you replace "-" (minus), but IMHO that id not present in the IDs anyways...?! (See my previous post about the ID's). Why do you do so?
--- End quote ---
Although "-" (minus) is valid as an XML element name, TiXml apparently decides that they should be synonymous with, and written as "_" (underscores). The change I made to the ID creation algorithm allows "-" to be used internally (I mostly did this for the cosmetic purposes of naming the XML files: options_arm-elf-gcc.xml is more recognizable than options_armelfgcc.xml, which is what it would have been under the previous system).
--- Quote from: jens on August 03, 2012, 11:26:32 am ---This should be stated in the label, or if possible the compiler should be reloaded automatically.
--- End quote ---
This patch causes the compilers to be reloaded (if chkNonPlatComp changed) when the settings dialog is dismissed; I did not do this at first because I was worried about possible side effects, however it seemed to function as expected in my few test cases.
(Sorry about the build issues.)
Jenna:
Applied in the branch, with one little change:
if abuild is active the settings will not be applied, because unloading and loading compilers might lead to problems.
Alpha:
--- Quote from: Alpha on August 02, 2012, 11:35:29 pm ---
* Switch the right-click note to a tool tip (this is less obtrusive, but should still alert the user to the editing capability)
--- End quote ---
By the way, am I correct in assuming the revert of this means that a visible note is preferred over a tool tip?
killerbot:
when working on the silencing of some warnings, I did the following.
I added for example on the GLOBAL compiler level some directives (-std=c++0x, or -fpremissive, or ...)
Then I rebuild CB with CB, the new directives take effect, but then then generate new unwanted warnings, because then they are also provided to gcc, in case its building c sources (like the depslib), which made me think. Shouldn't those compiler options be categorized (C, C++, both) , and have our system being smart enough that when he sees a C++ directive, but the current project is C, that he does not apply it ?
What do you think ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version