At 04:08 PM 3/2/2006, you wrote:
>Am Donnerstag März 2 2006 20:39 schrieb William A. Hoffman:
>> I found the problem with your example and checked in a fix into CVS.
>> The try_compile command was not sending the value of CMAKE_MOUDLE_PATH
>> into the try compile project.
>
>Thanks! It works now. I
[I think the cc to the list got lost]
Am Donnerstag März 2 2006 20:39 schrieb William A. Hoffman:
> I found the problem with your example and checked in a fix into CVS.
> The try_compile command was not sending the value of CMAKE_MOUDLE_PATH
> into the try compile project.
Thanks! It works now. I
Am Donnerstag Februar 23 2006 16:40 schrieb William A. Hoffman:
> At 10:43 AM 2/23/2006, Prakash Punnoor wrote:
> >Now another question: nasm cannot link code, so what should I write into
> >CMAKE_ASM_LINK_EXECUTABLE? It should use the default c/c++/whatever
> > linker.
>
> It should run the link c
At 10:43 AM 2/23/2006, Prakash Punnoor wrote:
>Now another question: nasm cannot link code, so what should I write into
>CMAKE_ASM_LINK_EXECUTABLE? It should use the default c/c++/whatever linker.
It should run the link command directly.
>Why does TRY_COMPILE not only compile but also try to l
Am Sonntag Februar 19 2006 22:30 schrieb Prakash Punnoor:
> Hi,
>
> I am using these files to get nasm support:
> http://www.cmake.org/pipermail/cmake/2005-November/007478.html
>
> This works for compilation, but recently I wanted to make a test using
> TRY_COMPILE like this:
>
> # check nasm
Hi,
I am using these files to get nasm support:
http://www.cmake.org/pipermail/cmake/2005-November/007478.html
This works for compilation, but recently I wanted to make a test using
TRY_COMPILE like this:
# check nasm visibility support
SET(SOURCE "global _foo:function hidden")
