From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Jesse Corrington
Sent: 12 December 2007 00:46
To: cmake@cmake.org
Subject: [CMake] turning off compile testing
Is there any way to turn off try compile during configuration?
We do it this way:
cmake
Hi all,
I am developing a library and usign cmake as a building tool.I want to test
my library when building. Directory structure is like this::
-src
|_ lib_src1.cpp
|_ lib_src2.cpp
|_ lib_src3.cpp
-test
|_ test.cpp
I wrote CMakeLists.txt in src folder and it is working
Hi all,
I am developing a library and usign cmake as a building tool.I want to test
my library when building. Directory structure is like this::
-src--lib_src1.cpp
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi Again,
FWIW here's how I managed to have mangled names in the output *and* in the
right folder instead of $(OutDir).
project(FOO)
add_library(FOO foo.cpp)
set_target_properties( FOO PROPERTIES DEBUG_OUTPUT_NAME foo-debug
RELEASE_OUTPUT_NAME foo-release)
add_custom_command(TARGET FOO
Josef Karthauser wrote:
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Jesse Corrington
Sent: 12 December 2007 00:46
To: cmake@cmake.org
Subject: [CMake] turning off compile testing
Is there any way to turn off try compile during configuration?
We do it this way:
cmake
-Original Message-
We do it this way:
cmake -DCMAKE_CXX_COMPILER_WORKS=1 -DCMAKE_C_COMPILER_WORKS=1
-DHAVE_CMAKE_SIZEOF_VOID_P=1 .
That looks like a bad idea to me The void one in particular. You
should really be careful about setting stuff like this by hand
Are your source and binary directories on different drive letters? Does the
problem occur if you use C: instead of Z: for the binary tree?
On 12/12/07, Cem DEMiRKIR [EMAIL PROTECTED] wrote:
Hi David,
Unfortunately it doesn't work. It produces the same errors.
Regards
Cem
No, David, it still continues producing the same error as before. I've
changed the Bin directory to D:\Test and it still produces the error.
Regards
Cem
_
From: David Cole [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 6:50 PM
To: Cem DEMiRKIR
Cc: CMake Mailing
Hi, David
And also tested it for C: and it doesn't work either.
Regards
Cem
_
From: David Cole [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 13, 2007 6:50 PM
To: Cem DEMiRKIR
Cc: CMake Mailing List
Subject: Re: [CMake] What's happening to CMake ??? Please help !!!
Hey
I have very strange problem using cmake (cmake version 2.4-patch 7, from
packages) on debian. I have small progam : time.cpp. It uses boost_date_time
library. It compiles fine with g++ time.cpp -lboost_date_time.
So I try to write CMakeLists.txt for that:
$ cat CMakeLists.txt
SET
Cem DEMiRKIR wrote:
No, David, it still continues producing the same error as before. I've
changed the Bin directory to D:\Test and it still produces the error.
Run cmake from the command line with --debug-trycompile. Then go into
CMakeTmp and look at the project that is created, and try
Sorry, I forgot to add make output:
make
Scanning dependencies of target time
[100%] Building CXX object CMakeFiles/time.dir/time.o
Linking CXX executable time
CMakeFiles/time.dir/time.o: In function
`boost::date_time::month_formatterboost::gregorian::greg_month,
Did you build the Data_Time boost library? Are you linking against
the libboost_date_time library? Run a 'make VERBOSE=1' and post
the ouput.
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Dec 13, 2007, at 1:19 PM, Tomasz Kalkosiński wrote:
the below line should be something like:
TARGET_LINK_LIBRARIES ( time ${Boost_Date_Time_Library} )
Look at the FindBoost.cmake file for the exact name of the library
variable. The way you had the line you would be including a directory
and not the actual boost date_time library.
--
Mike
I'm trying to add a prebuild custom command to a NMake target, but it
doesn't appear to be running in the right place.
Here's an example:
CMakelists.txt:
Project(Hello)
add_library (Hello hello.cxx hello.h)
add_custom_command(TARGET Hello PRE_BUILD
COMMAND ${CMAKE_COMMAND}
Not sure if this is know but using today's cvs I tried the following:
504:[EMAIL PROTECTED]:bin]$ cmake --help-Variable-list /tmp/out.txt
CMake Error: The source directory /tmp/out.txt does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Bug?
Also, there is a
Mike Jackson wrote:
Not sure if this is know but using today's cvs I tried the following:
504:[EMAIL PROTECTED]:bin]$ cmake --help-Variable-list /tmp/out.txt
CMake Error: The source directory /tmp/out.txt does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Mike Jackson wrote:
Not sure if this is know but using today's cvs I tried the following:
504:[EMAIL PROTECTED]:bin]$ cmake --help-Variable-list /tmp/out.txt
CMake Error: The source directory /tmp/out.txt does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Bug?
On 2007-12-12 17:10-0800 Alan W. Irwin wrote:
A set of custom rules to copy files from the source tree to the build tree
is screwing up for parallel builds on Debian testing with cmake 2.4.7.
Here is part of the make -j 2 output:
make -f
doh.. cmake 2.4.7 was on my path. I should have done:
bin/cmake --help-variable-list /tmp/variable.html
sorry for the noise
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Dec 13, 2007, at 3:09 PM, Bill Hoffman wrote:
Mike Jackson wrote:
Not sure
Alan W. Irwin wrote:
My obvious next step is to try and make a simple CMake example that
reliably
reproduces the bug, but this is such an important bug (at least for those
with access to multiprocessors who want to use parallel builds) that I
thought the above result was worth reporting
Mike Jackson wrote:
doh.. cmake 2.4.7 was on my path. I should have done:
bin/cmake --help-variable-list /tmp/variable.html
sorry for the noise
Actually, you did find a bug, and I have fixed the docs with the wrong
case for the v.
-Bill
___
Here is another one:
531:[EMAIL PROTECTED]:Build]$ bin/cmake --help-module-list
cmake version 2.5-20071213
Internal error: Modules list is empty.
532:[EMAIL PROTECTED]:Build]$ bin/cmake --version
cmake version 2.5-20071213
--
Mike Jackson Senior Research Engineer
Innovative Management
Hi,
I was talking to Miguel about the recent FindwxWidgets changes because
they didn't work out on for static libraries on a Mac.
Summarizing the issue is that CMake makes the (wrong) assumption that
what you want to add are shared libraries (at least on a Mac).
Let me explain in more detail
Hi Pau Garcia i Quiles,
Thanks for the suggestion. It works well on linux and Windows.
However, it is still not happy with MinGW. To compile with MinGW, we
need to have
TARGET_LINK_LIBRARIES( my_lib ITKCommon ITKIO libxml2)
and set ${LIBXML2_LIBRARIES} in CMake GUI to the directory where
The mac linker is unique in how it searches for libraries. The
linker will *always* pick the shared library over the static one if
it finds a shared one first or at the same time. Also the order it
searches the library path list is different than on other *nix systems.
By default the
On 2007-12-13 15:39-0500 Bill Hoffman wrote:
Alan W. Irwin wrote:
My obvious next step is to try and make a simple CMake example that
reliably
reproduces the bug, but this is such an important bug (at least for those
with access to multiprocessors who want to use parallel builds) that I
2007/12/12, Marcus [EMAIL PROTECTED]:
In the past (when I was using SCons) I compiled the source files into
object files, and then linked the same object files into both the test
executable and the shared library. Is it possible to do this with CMake?
As far as I know there's no official
Hello every expert:
I have one c++ code (.cxx file) with a CMakeLists.txt file, this program need
ITK, I have already setup everything ready in my linux machine.
I have built a binary file by following steps:
1) ccmake ., setup the ITK path, configuration and generation
2) make
Now I want to
Alan W. Irwin wrote:
It was good to hear that make -j N normally works with CMake.
Yes indeed. I frequently run make -j70 across a 35-host dual-CPU
cluster using distcc, and every time I've updated CMake's files, it's
correctly rebuilt the makefiles before continuing.
b
Alan W. Irwin wrote:
So just keeping narrowly focussed on that fragment there is only one ALL
custom target and ADD_DEPENDENCIES would not help since it only works on
targets. Thus, I doubt there is anything locally wrong with dependencies
there. It is possible some other dependency is
Well, as far as I know you can take the .a-file with linking to the
full path... I don't know why CMake doesn't keep the parameters I give
them? Probably if I add the libraries to the linking variables, it
would take them, but that's not the point :S... If I pass CMake a full
static path, I expect
I have been experimenting with cmake for some time now and finally have
it generating project files for all of my libraries, dlls, and
executables except for one. The lone hold out is a C++/CLI WinForms app.
Before I spend too much time on it, does anyone know if it's even possible?
Thanks,
On 2007-12-13 17:07-0500 Brad King wrote:
Alan W. Irwin wrote:
So just keeping narrowly focussed on that fragment there is only one ALL
custom target and ADD_DEPENDENCIES would not help since it only works on
targets. Thus, I doubt there is anything locally wrong with dependencies
there. It
Alan W. Irwin wrote:
So the rule seems to be that parallel builds do not work if there are two
or more separate custom targets that file depend directly or indirectly
(via
some custom command file dependency chain) on the same output files.
Another way of summarizing these results is that
Hi, I've being trying cmake 2.5 from CVS and I've come with some
unwanted semicolons in compiler flags. Tracing this down, I've found
that CMAKE_CXX_FLAGS (and CMAKE_C_FLAGS, etc...) is initialized with a
space, so that
CMakeLists.txt:
message(X ${CMAKE_CXX_FLAGS} X)
outputs:
X X
instead of:
XX
On 2007-12-13 19:15-0500 Brad King wrote:
Alan W. Irwin wrote:
So the rule seems to be that parallel builds do not work if there are two
or more separate custom targets that file depend directly or indirectly
(via
some custom command file dependency chain) on the same output files.
Another
Bill Hoffman escreveu:
Do you have environment variables CFLAGS and CXXFLAGS set to have just a
space? Also, what OS/compiler are you using?
No, those variables are empty. Here's my configuration
[EMAIL PROTECTED] ~ $ cmake --version
cmake version 2.5-20071212
[EMAIL PROTECTED] ~ $ echo
On 2007-12-13 18:45-0800 Alan W. Irwin wrote:
Brad, I am struggling with understanding the recursive make system that
CMake normally employs so I am having trouble following the complete
Makefile logic that my simple example creates. However,
CMakeFiles/tclIndex_examples_tcl2.dir/build.make
Hi, is there a way to inform cmake that it should ignore the return code
of the command specified with add_custom_command? I want the command to
be successful, even if it returns something different than 0.
For instance:
add_custom_command(OUTPUT text.cpp COMMAND false)
add_executable(test
On Dec 13, 2007 11:05 PM, Rodolfo Lima [EMAIL PROTECTED] wrote:
Hi, is there a way to inform cmake that it should ignore the return code
of the command specified with add_custom_command? I want the command to
be successful, even if it returns something different than 0.
For instance:
41 matches
Mail list logo
