On 09/13/2010 05:46 PM, Gerhard Stengel wrote:
> Hi,
>
> I have a strange problem with custom targets and their dependencies. I do as
> follows:
>
> 1) create a file 1 and add it to a custom target 1
> 2) create a file 2 and add it to a custom target 2
> 3) create a 3rd file by packing #1 and #2
On 9/13/10 12:29 PM, David Aldrich wrote:
Hi
I have tried to set the output directory for my library as follows:
# set destination directory for LIBRARY target (i.e. libKernel.a)
set( CMAKE_LIBRARY_OUTPUT_DIRECTORY ./_gnuRelease )
# build the Kernel static library
add_library(Kernel STATIC ${
Hi
I have tried to set the output directory for my library as follows:
# set destination directory for LIBRARY target (i.e. libKernel.a)
set( CMAKE_LIBRARY_OUTPUT_DIRECTORY ./_gnuRelease )
# build the Kernel static library
add_library(Kernel STATIC ${SRCS})
however, the library is being create
if(APPLE)
set(CMAKE_OSX_DEPLOYMENT_TARGET 10.5)
endif()
Hope this helps!
Ryan
On 9/10/10 9:19 AM, Pedro d'Aquino wrote:
The problem wasn't related to the universal binaries, but to the SDK
used (10.5). I need to add "-mmacosx-version-min=10.5" to the compiler
flags in order to make it wo
On Mon, Sep 13, 2010 at 06:01:52PM +0200, Olivier Pierard wrote:
> - add_test( mpirun -machinefile $TMPDIR myexec ) => will never expand
> TMPDIR - I don't understand why because in CTestTestfile.cmake, I have
> add_test( test_name "mpirun" "-machinefile" "$TMPDIR" "myexec"); if I
> submit this as
Dear all,
I re-submit a previous question with no answer in a simpler way.
A ctest_test() call on a cluster computation node executes a test
constructed with add_test(..) on the cluster master node.
add_test contains an evironment variable but is not expanded or expanded
at configuration time bu
Hi,
I have a strange problem with custom targets and their dependencies. I do as
follows:
1) create a file 1 and add it to a custom target 1
2) create a file 2 and add it to a custom target 2
3) create a 3rd file by packing #1 and #2 together
4) the 3rd file is added to a custom target which dep
Philip,
You closed the bug already so I can't comment there, but I wanted to let you
know that this latest version of FindBoost.cmake did work as expected for me.
Thank you so much for your help.
--
Shane
From: philiplow...@gmail.com [mailto:philipl
Hi Michael
I have found that I had an 'add_executable' call left in accidentally.
Sorry for wasting your time. It works well now. Thanks again for your help.
BR
David
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:
On 13. Sep, 2010, at 14:57 , David Aldrich wrote:
> Hi Michael
>
>
>> You never link static libraries. They are more like zip files than actual
>> libraries and just contain the compiled object files and for if you ran
>> ranlib on it, also a "table-of-contents" to speed link up.
>>
>> If you
Hi Michael
> You never link static libraries. They are more like zip files than actual
> libraries and just contain the compiled object files and for if you ran
> ranlib on it, also a "table-of-contents" to speed link up.
>
> If you do "target_link_libraries" in CMake, where the target is a sta
Hi,
I am using CMAKE for the first time and ive run into a problem. Basically i
have set where the source is and where to build the binaries. Then i add an
entry. But when i configure the program seems to have trouble finding my
compiler. I have Visual Studio 2008 Express Edition installed on a Wi
On 13. Sep, 2010, at 13:03 , David Aldrich wrote:
> Hi Michael
>
>> set(SRCS a.c b.c d.c e.c)
>>
>> add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/f.c
>> COMMAND ...
>> DEPENDS ${SRCS}
>> COMMENT "Generating f.c"
>> VERBATIM)
>> list(APPEND SRCS ${CMAKE_BINARY_DIR}/f.c)
>>
>> add_executable
Hi Michael
> set(SRCS a.c b.c d.c e.c)
>
> add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/f.c
> COMMAND ...
> DEPENDS ${SRCS}
> COMMENT "Generating f.c"
> VERBATIM)
> list(APPEND SRCS ${CMAKE_BINARY_DIR}/f.c)
>
> add_executable(main ${SRCS})
Thanks - that worked nicely.
Now I have anoth
14 matches
Mail list logo
