Ok, now that we have collected a list of problems/facts, I have the
feeling that
we need to step back and make a wishlist... There is no way in writing an
all-purpose version scripts since there exist contradictory paradigms.
I will start by the list of problems/facts:
* BLAS and CBLAS do have
hi, i'm building a unix project.
i want to add -lpthread -lrt -ldl -lnsl to all executables.
when i use set_target_prop with link_flags, those lib are placed right after
the compile flags.
when i use set(cmake_standard-libraries libpthread.so ...) nothing happen i
don't even know where this
Hi all,
I got the impression, that the CMake generator for Visual Studio 7
ignores the working directory set in ADD_CUSTOM_COMMAND. Is this a bug
or is this a documented feature somehow?
Or am I simply doing something wrong?
Regards,
Martin
Virus checked by G DATA AntiVirus
Target_link_Libraries (Executable pthread rt dl nsl)
If those libraries are in the standard locations gcc should be able
to pick them up ok.
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Jun 26, 2008, at 5:44 AM, Ingrid Kemgoum wrote:
hi, i'm
Hi,
I'm currently trying to setup cmake for creating visual studio 2005/2008
solution files linking against windows mobile 5/6. I've read a few
postings from September-November 2007 about that issues, but I finally
did not find a closed-form solution to this.
Has anyone worked around all
Martin Apel wrote:
Hi all,
I got the impression, that the CMake generator for Visual Studio 7
ignores the working directory set in ADD_CUSTOM_COMMAND. Is this a bug
or is this a documented feature somehow?
Or am I simply doing something wrong?
Might be a bug, might be you. Please provide a
hi,
i'm using cmake with Unix and
i have a problem with the size of my executable.
it's 20 Ko more than what's due (compared with a hand done makefile)
it this not a problem of preprocess files and other things done with cmake
before building the executable?
thanks
Are the compile flags _exactly_ the same such as optimization level
and debug symbols?
in your cmake build directory run make VERBOSE=1 to see what gcc is
using and then compare that to your own makefile.
--
Mike Jackson Senior Research Engineer
Innovative Management Technology
Hi Bill
I simply do the following:
ADD_CUSTOM_COMMAND(OUTPUT ${FSrcWithBinDir}
${CMAKE_CURRENT_BINARY_DIR}/accessor_protos.h
COMMAND ${CMAKE_COMMAND} -E copy_if_different
${CMAKE_CURRENT_SOURCE_DIR}/FortranModules.inp
${CMAKE_CURRENT_BINARY_DIR}/FortranModules.inp
Martin Apel wrote:
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
For VS this is the default working directory if no WORKING_DIRECTORY is
given.
This calls a perl script to generate a bunch of Fortran files as needed.
This script has to run in the output directory. I have
On 2008-06-26 09:56+0200 Hauke Heibel wrote:
2) FindCBLAS.cmake:
---
a) Well, we need it (I already told Alan, that I am willing to write it)
b) Should be able to use FindBLAS.cmake (Legacy BLAS is required by CBLAS),
even without a Fotran compiler being present...
In the
I just checked in a change for feature request #6191, you can now (in CVS
CMake) use parentheses in if and while command conditionals. E.g.
if (2 GREATER 1 AND (4 LESS 3 OR 5 LESS 6) AND NOT (7 GREATER 8))
message()
endif()
evaluation of parenthetical groups has the highest order of
Quoting Ken Martin [EMAIL PROTECTED]:
Cool, thanks!
I just checked in a change for feature request #6191, you can now (in CVS
CMake) use parentheses in if and while command conditionals. E.g.
if (2 GREATER 1 AND (4 LESS 3 OR 5 LESS 6) AND NOT (7 GREATER 8))
message()
endif()
evaluation
On Thursday 26 June 2008, Pau Garcia i Quiles wrote:
Quoting Ken Martin [EMAIL PROTECTED]:
Cool, thanks!
Nothing to add, cool :-)
Alex
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Funny, I just got back to this project on windows and the below code
doesn't actually work. Sorry for the noise.
Mike A. any chance you would like to share what you came up with?
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Jun 18, 2008, at
Hello,
I'm not sure if I should direct this to the vxl mailing list, but I
think this is a ctest issue...
I have a CTest Script that I'm using to build and submit to the vxl
dashboard. It can be viewed at:
http://www.cdash.org/CDash/viewNotes.php?buildid=109301
The problem is that the vxl
I just ran into this as well. It appears that instead of CMake
telling you that a file is missing during configuration, it simply
throws the assert during generation.
You can reproduce this with the following CMakeLists.txt file (no
source file needed).
project(test)
set(sources foo.cc)
James Bigler wrote:
I just ran into this as well. It appears that instead of CMake
telling you that a file is missing during configuration, it simply
throws the assert during generation.
You can reproduce this with the following CMakeLists.txt file (no
source file needed).
project(test)
On Thursday 26 June 2008, Clemens Arth wrote:
Hi,
I'm currently trying to setup cmake for creating visual studio 2005/2008
solution files linking against windows mobile 5/6. I've read a few
postings from September-November 2007 about that issues, but I finally
did not find a closed-form
On Thu, Jun 26, 2008 at 3:10 PM, Bill Hoffman [EMAIL PROTECTED] wrote:
James Bigler wrote:
I just ran into this as well. It appears that instead of CMake
telling you that a file is missing during configuration, it simply
throws the assert during generation.
You can reproduce this with the
This is the same as the mantis issue
http://public.kitware.com/Bug/view.php?id=6799 which I closed on 6/19. It is
fixed already in CVS HEAD and in CVS CMake-2-6 branch. But it is still
repeatable in CMake 2.6.0.
On Thu, Jun 26, 2008 at 5:45 PM, James Bigler [EMAIL PROTECTED] wrote:
On Thu,
21 matches
Mail list logo
