Code::Blocks Forums
User forums => Help => Topic started by: hongxing on April 23, 2007, 03:15:06 pm
-
I am now using Intel C++ Compiler (ICC) for Linux 9.1.0.45. My Linux distribution is SuSE Linux Enterprise Server 10. ICC is installed in /opt/intel by default.
My CB is generated from the svn head source code. In CB, I set the ICC as the default compiler, but when compiling, it says that:
"test - Debug" uses an invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]. Skipping...
Nothing to be done.
My question is :
1. how to config to use ICC in CB in Linux? (I only found document about using ICC in windows with CB)
2. After I install ICC and CB, when first CB is starting, the Compilers auto-detection dialog only detects and
find the GNU GCC Compiler, but not Intel C/C++ Compiler, why?
thanks in advance!
-
can anyone help?
Or maybe it's impossible to integrate ICC with CB on Linux ?
-
Actually the default path is not correct. Go to Settings > Compilers and debuggers menu. Select Intel C/C++ compiler from the Selected compiler combo box.
Now select Toolchain executable option from the combo below Selected compiler combo.
Change the Compiler installation directory from /opt/intel/cc/9.0 to the actual path. In my PC, the actual path is /opt/intel/cc/9.1.045 and the last part of this installation path will vary upon installed compiler version and this makes auto-detection difficult. Set this path and your Intel compiler is ready.
Regards,
Biplab
-
thanks I will try it
-
I've updated the Autodetection code. Now C::B should be able to detect it automatically in Linux. :)
Regards,
Biplab
-
Shouldn't "Autodetection" better be renamed to "Look out for the Compiler in its default installation path"? ;-)
Now seriously. For beginners this might be confusing when they installed i.e. MINGW with its installer to c:\Program Files\MingW and CB won't find it.
I know real autodetection is hard, i just think the wording for this dialog should explain its inner workings a little bit better.
greets
Markus
-
Shouldn't "Autodetection" better be renamed to "Look out for the Compiler in its default installation path"? ;-)
The name is too long for a button.. ;)
May be we can inform user to change the settings manually once Autodetection fails. :)