User forums > Using Code::Blocks

Settings for Installing Intel Compiler v11

(1/3) > >>

cdemirkir:
Hi Everyone,

   I'd like to use Intel Compiler v11 as default compiler in C::B. I applied the similar settings defined in http://wiki.codeblocks.org/index.php?title=Installing_a_supported_compiler#Intel_C.2B.2B_Compiler as the following

For executables:
C:\Program Files\Microsoft Visual Studio 8\VC\bin
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE
Z:\Libraries\Microsoft SDKs\Windows\v6.1\bin

For includes:
C:\Program Files\Intel\Compiler\11.0\066\cpp\include
C:\Program Files\Microsoft Visual Studio 8\VC\include
Z:\Libraries\Microsoft SDKs\Windows\v6.1\Include

For libraries :
C:\Program Files\Intel\Compiler\11.0\066\cpp\bin\ia32\lib
C:\Program Files\Microsoft Visual Studio 8\VC\lib
Z:\Libraries\Microsoft SDKs\Windows\v6.1\Lib
 
   Then I tried the compile a source which uses OpenCV library include file, cxmisc.h, and gives an error in the following preprocessor check lines of the header file and exits, which means it goes the last #elif condition. When I check if the C::B can find the definition of WIN32, it can find the definition of this macro in Ole2.h of the SDK header but it can the definition of _MSC_VER and therefore I guess, it it goes till last #elif preprocessor condition which is equal to the error condition. I can not see the reason of this error. I'd be grateful to anyone who can help me resolve this issue ?

Regards
Cem

/****************************************************************************************\
*                                  Common declarations                                   *
\****************************************************************************************/

/* get alloca declaration */
#ifdef __GNUC__
    #undef alloca
    #define alloca __builtin_alloca
#elif defined(WIN32) || defined(WIN64)
    #if defined(_MSC_VER) || defined(__BORLANDC__)
        #include <malloc.h>
    #endif
#elif defined HAVE_ALLOCA_H
    #include <alloca.h>
#elif defined HAVE_ALLOCA
    #include <stdlib.h>
#elif   <------------GIVES ERROR AT THIS CONDITION
    #error
#endif

I can not find the reason of that _MSCVER can not be recognized by the compiler ....

ollydbg:
can intel compiler build OpenCV project sucessfully?
I have used MinGW and Visual C++ compiler, but I never heart it can be compiled by Intel compiler in the OpenCV forum.

cdemirkir:

--- Quote from: ollydbg on March 29, 2009, 04:23:53 am ---can intel compiler build OpenCV project sucessfully?
I have used MinGW and Visual C++ compiler, but I never heart it can be compiled by Intel compiler in the OpenCV forum.

--- End quote ---

OpenCV can be compiled with Intel Compiler, see the INSTALL file in OpenCV root directory to read the details.

cdemirkir:

--- Quote from: CBLaw on March 29, 2009, 05:07:48 am ---Eventhough it looks like #defines aren't set right for some unknown reason, you may be able to force it to work.  If I were you, I'd comment out the whole #ifdef block and try replacing it one by one with one of those three #includes until it works (or not!!!). Try #include <malloc.h>, if it doesn't like that, try #include <stdlib.h>, and finally try #include <alloca.h>

Not a great answer I know, just something to try until someone who knows what they are doing can help!!!

Good luck. Lemme know how you like the Intel compiler. I really want to try it.

--- End quote ---

The reason for preferring Intel Compiler to GCC, GCC produces compiling problems with OpenMP directives.

ollydbg:

--- Quote from: cdemirkir on March 29, 2009, 08:14:05 am ---The reason for preferring Intel Compiler to GCC, GCC produces compiling problems with OpenMP directives.

--- End quote ---

For testing, I just successfully built svn opencv libraries with TDM-Mingw 4.3.3 with OpenMP enabled :D.
No compiling problems happened if you follow the readme supplied my TDM package.

You can have a try.
Good luck.

Navigation

[0] Message Index

[#] Next page