Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Intel C++ Compiler Support
polygon7:
--- Quote from: Ptomaine on October 21, 2005, 09:21:07 pm ---It has its own command line options for optimization and code generation. It's hard to tune a project if an IDE has no support for them. That's why I create this forum thread. (...) Is it hard to implement the feature I ask?
--- End quote ---
http://forums.codeblocks.org/index.php/topic,604.0.html
Ptomaine:
Thank you good guy polygon7
Sorry, I didn't notice your previous hint :?
Thanks again.
P.S. But I think Code::Blocks might support it natively 8)
rickg22:
I agree! This way we can get rid of the manual config. Stuff - after all, if we could manage to add other compilers, how hard will it be to clone one? I'm sure it will be easier to have ONE programmer to add it, than having to do tech support about 10 times :P
Now, If I only knew how to add the compilers internally... :oops:
mandrav:
--- Quote from: rickg22 on October 22, 2005, 01:06:54 am ---I agree! This way we can get rid of the manual config. Stuff - after all, if we could manage to add other compilers, how hard will it be to clone one? I'm sure it will be easier to have ONE programmer to add it, than having to do tech support about 10 times :P
Now, If I only knew how to add the compilers internally... :oops:
--- End quote ---
Rick's new task: add Intel compiler support :P
For anyone interested, steps to add native support for the INTEL (or any other) compiler:
[*] Copy compilerMSVC.(cpp|h) to compilerINTEL.(cpp|h). (in plugins/compilergcc).
[*] Adjust contents of compilerINTEL.cpp to support the new compiler.
[*] Add #include "compilerINTEL.h" in compiler.gcc
[*] In compilergcc's constructor, where it says "// register built-in compilers", add "CompilerFactory::RegisterCompiler(new CompilerINTEL);"
[*] Build.
[/list]
Urxae:
--- Quote from: mandrav on October 22, 2005, 09:19:41 am ---For anyone interested, steps to add native support for the INTEL (or any other) compiler:
[*] Copy compilerMSVC.(cpp|h) to compilerINTEL.(cpp|h). (in plugins/compilergcc).
[*] Adjust contents of compilerINTEL.cpp to support the new compiler.
[*] Add #include "compilerINTEL.h" in compiler.gcc
[*] In compilergcc's constructor, where it says "// register built-in compilers", add "CompilerFactory::RegisterCompiler(new CompilerINTEL);"
[*] Build.
[/list]
--- End quote ---
In this case it would seem to be a bit more complicated as Intel C++ seems to accept different command-line parameters on Windows and Linux.
If it doesn't also have a "common" set of parameters that'll work on both (and represents the entire range of possible options the other ones do), supporting it on both platforms might be a bit more work than your average compiler. You might have to either use a lot of #ifdefs in the file, or even use separate files for the Windows and Linux version.
The last one may be preferable if remote developement support is planned as you could then have both versions on your system at the same time, one for your local OS and one for the remote OS.
Of course, I haven't really checked if the supported parameter sets are actually different or if they just swap out '/' (Windows) and '-' (Linux) prefixes when on the other platform. I'm not sure if it's even possible (are there any MSVC command-line parameters that mean something else to GCC?), but if the latter is the case a simple checkbox in the options would probably suffice. Should default to the setting for platform you're currently running, of course.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version