Quantcast

Re: help using try_run with custom build type

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: help using try_run with custom build type

George Neill
Hi All,

On Wed, Jul 8, 2009 at 2:29 AM, Denis
Scherbakov<[hidden email]> wrote:

>
>> > It appears to fail because the compiler options do not
>> make it in when
>> > creating the executable ... is there something silly I
>> have missed?
>> > Also, I was wondering why TRY_RUN doesn't use the
>> default flags
>> > defined from CMAKE_BUILD_TYPE ?
>
>
>> Is this a bug or am I not using TRY_RUN correctly?
>
> I am not sure that I understood correctly, but once I had a problem passing
> compiler flags to TRY_COMPILE. I solved it by stuffing compile flags into
> CMAKE_FLAGS -DCOMPILE_DEFINITIONS:STRING=${MY_COMPILE_FLAGS}
>
> I think TRY_RUN is the same.

What's the difference between,

  TRY_RUN( ... COMPILE_DEFINITIONS
"${CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE}}"  ... )

and

  TRY_RUN( .. CMAKE_FLAGS
-DCOMPILE_DEFINITIONS:STRING="${CMAKE_C_FLAGS_${CMAKE_BUILD_TYPE}}"
...)

I realize the latter is passed as a command line option, but, Is the
first definition only supposed to contain [-/]D compiler macros, while
the latter can contain actual compiler flags?

TIA,
George
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Loading...