The ninja targets generated by cmake for our project have the .o targets
used to build libraries that have order-only dependencies on the dynamic
libraries to which the resulting library will be linked. That is
- libfoo.so is built from foo.o and libbar.so
and
- foo.o has an order-only dependency
. It is run by cmake as well as by git.
On Jun 13, 2013, at 7:06 AM, Daniel Russel drus...@gmail.com wrote:
As a counter example (which perhaps could be improved on), we are currently
putting our generated cmake files in the build tree. The reason for this to
allow git post-checkout and post-rewrite
I'm running into trouble getting paths with spaces in them to propagate
cleanly through my cmake scripts and end up with a lot of thrashing with
changes that work with one cmake version/generator and then fail with
another. Does anyone have rules that they use to write cmake files that
result in
Is one supposed to be able to mix -L -LE arguments to ctest? I'd like to
(eg run all tests for a module that aren't marked as expensive), but I'm
confused by what I get.
For example, if I do ctest -L IMP.em2d I get:
Label Time Summary:
IMP.em2d= 367.96 sec
example = 141.11 sec
I'm not very clear on how cmake chooses which compiler it uses by default.
Specifically, we have a system where a there is an old version of gcc installed
in the system and then a newer version installed elsewhere, but in the PATH (so
running g++ or gcc finds the new version). However, cmake
I'm trying to use find_path() and find_library() to detect if a certain library
is already in the system and, if not, build it myself. They find functions seem
to find files that are located in CMAKE_INSTALL_PREFIX/lib etc (when
CMAKE_INSTALL_PREFIX is a non-standard path). I'd kind of like to
I'm using the shipped UseSWIG package to add a swig module to my project (cmake
2.8). For those that don't know, swig works by running the swig command on an
input file (a .i) and then building the files that it produces. The input file
tells swig to scan certain header files and the output
I'm trying to get cross compilation of a simple library working to build a
windows library on a linux box using the visual studio compilers. So far the
farthest I've gotten is with:
./cmake-2.8.9-Linux-i386/bin/cmake ../rmf -DCMAKE_SYSTEM_NAME=Windows
-DCMAKE_C_COMPILER=/usr/bin/cl
On Oct 15, 2012, at 9:35 PM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
On 2012-10-15 21:02-0700 Daniel Russel wrote:
I'm trying to get cross compilation of a simple library working to
build a windows library on a linux box using the visual studio
compilers.
I don't get it. How can
