The following issue has been SUBMITTED.
==
http://www.itk.org/Bug/view.php?id=13029
==
Reported By:Fabian Hachenberg
Assigned To:
Hi all,
People interested in discussing a new flexible way to create package file name
with CPack may follow/throw ideas on the concerned feature request on
the tracker:
http://www.cmake.org/Bug/view.php?id=12997
Philip has volunteered to work on this,
I'll be reviewing/helping as much as I can.
Hi,
We found a scenario when when ctest does not detect a build error.
This occurs when clang is invoked as a linker and one of the libraries is not
found:
/Developer/usr/bin/clang++ -LDIR1 -LDIR2 -lib1 -lib2 -lib3 [...] -o MyApp
ld: library not found for -lprofile_rt
Command
I am wondering if we want to call the Ninja generator something like:
Ninja Makefiles... It is not totally accurate, but it avoids code like
this:
IF(CMAKE_GENERATOR MATCHES Makefiles OR CMAKE_GENERATOR MATCHES Ninja)
Also, it is more likely to work with existing cmake build files. I had
Hi Brad,
I investigated this issue a bit more. I have two conclusions.
[1]
Clang generates clear error messages, and ctest detects such errors without
problem. These errors look like this:
ld: library not found for -lkaboom
clang: error: linker command failed with exit code 1 (use -v to
On Thu, Mar 08, 2012 at 05:44:09PM -0500, Bill Hoffman wrote:
I am wondering if we want to call the Ninja generator something like:
Ninja Makefiles... It is not totally accurate, but it avoids code like
this:
IF(CMAKE_GENERATOR MATCHES Makefiles OR CMAKE_GENERATOR MATCHES Ninja)
Also,
On Thu, Mar 08, 2012 at 09:25:37PM -0500, Bill Hoffman wrote:
On 3/8/2012 8:37 PM, Alan W. Irwin wrote:
I think that would be confusing to users.
Could you define an internal variable (to identify those generators
that have Makefile-like characteristics) that could be tested instead
of
Hi Michael,
May be you could have a look at [1], [2] and [3]. It basically illustrates
how to moc a header a file and include at the end of cpp file.
Hth
Jc
[1]
https://github.com/commontk/CTK/blob/master/Libs/Testing/CMake/ctkMacroGenerateMocs.cmake
[2]
I am trying to use CMake for a small Java project that's part of a bigger C++
project.
I have a Java project that looks like that:
project(MyProject Java)
include_directories(${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/MyProject.dir)
add_library(MyProject
file1.java
file2.java
file3.java
On Thu, Mar 8, 2012 at 9:50 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
On Mar 7, 2012, at 11:43 AM, Andreas Pakulat wrote:
On 07.03.12 10:10:27, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the
On 08.03.12 06:39:37, Kedzierski, Artur CIV NSWC Corona, PA13 wrote:
I am trying to use CMake for a small Java project that's part of a bigger C++
project.
I have a Java project that looks like that:
project(MyProject Java)
On Thu, Mar 8, 2012 at 11:30 AM, Andreas Pakulat ap...@gmx.de wrote:
On 08.03.12 09:50:55, Michael Jackson wrote:
On Mar 7, 2012, at 11:43 AM, Andreas Pakulat wrote:
On 07.03.12 10:10:27, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
On 03/08/2012 05:40 PM, buzz clay wrote:
Hi,
I have not been able to find the answer to my current problem so I
thought I'd try a new post. Before diving into the details, please be
aware that the code I am writing compiles/runs perfectly with a personal
Makefile I wrote.
My code is
Hi all,
People interested in discussing a new flexible way to create package file name
with CPack may follow/throw ideas on the concerned feature request on
the tracker:
http://www.cmake.org/Bug/view.php?id=12997
Philip has volunteered to work on this,
I'll be reviewing/helping as much as I can.
Hi All,
I have been working on enhancing CPack documentation.
http://public.kitware.com/Bug/view.php?id=10067
Some fair amount of work has now reached 'master'.
The two main features are:
cpack --help-variable-*
cpack --help-command-*
command line options.
As you will see:
$ cpack
Hi!
for visual studio 10 I have enable_testing() and some test modules. the
problem is that the working directory is wrong.
I have set it using the WORKING_DIRECTORY option for add_test
(set to ${CMAKE_CURRENT_SOURCE_DIR}),
also in LastTest.log.tmp there is a line
WORKING_DIRECTORY
showing the
On Thu, Mar 8, 2012 at 2:59 PM, Jochen Wilhelmy j.wilhe...@arcor.de wrote:
Hi!
for visual studio 10 I have enable_testing() and some test modules. the
problem is that the working directory is wrong.
I have set it using the WORKING_DIRECTORY option for add_test
(set to
Is it possible to add, at build time, a revision number to the installer file
name produced by CPack? I understand that to get the revision number at build
time one must run a command and I have used that technique to generate a source
code header, but I cannot figure out how to apply it to the
On Thu, Mar 8, 2012 at 3:57 PM, Glenn Ramsey g...@componic.co.nz wrote:
Is it possible to add, at build time, a revision number to the installer
file name produced by CPack? I understand that to get the revision number at
build time one must run a command and I have used that technique to
I do something like this in my CPack file:
set(DREAM3D_VERSION_SHORT ${DREAM3DLib_VER_MAJOR}.${DREAM3DLib_VER_MINOR})
set(CPACK_PACKAGE_FILE_NAME
DREAM3D-${DREAM3D_VERSION_SHORT}-${CMAKE_SYSTEM_NAME})
Where the DREAM3D_Lib_VER_* variables are generated with a call to my SCM (git
in my case)
Hi Mike,
When, during the build process is the call to the SCM made? If it is at build
time, rather than cmake time, then how do you do it?
Glenn
On 09/03/12 10:15, Michael Jackson wrote:
I do something like this in my CPack file:
set(DREAM3D_VERSION_SHORT
The call is during CMake time. Which means you need to rerun cmake if your
repository version runs. I guess you could try an add_custom_command(...) and
run the SVN command to get the revision number and make it a prebuild step for
one of your targets. Then it should get run at every build.
--
Yes, you can use add_custom_command(...) to run a script to get the revision
number, but I don't think you can use that to alter CPACK_PACKAGE_FILE_NAME,
which has been set at cmake time.
Glenn
On 09/03/12 10:52, Michael Jackson wrote:
The call is during CMake time. Which means you need to
2012/3/8 Glenn Ramsey g...@componic.co.nz:
Yes, you can use add_custom_command(...) to run a script to get the revision
number, but I don't think you can use that to alter CPACK_PACKAGE_FILE_NAME,
which has been set at cmake time.
This true but how wouldn't a revision update trigger a CMake
On 09/03/12 12:00, Eric Noulard wrote:
2012/3/8 Glenn Ramseyg...@componic.co.nz:
Yes, you can use add_custom_command(...) to run a script to get the revision
number, but I don't think you can use that to alter CPACK_PACKAGE_FILE_NAME,
which has been set at cmake time.
This true but how
Hi,
Imported library has scope in the directory in which it is created and
below.
If I want to use this library in parent scope, what should I do?
for example,
top CMakeLists.txt
add_subdirectory(sub)
add_executable(myapp main.cpp)
target_link_libraries(myapp imported_lib)
sub CMakeLists.txt
On Wed, Mar 07, 2012 at 07:14:52AM +0100, Nicolas Desprès wrote:
On Tue, Mar 6, 2012 at 8:58 PM, Clifford Yapp cliffy...@gmail.com wrote:
We *could*, if popular demand is high enough, merge it in anyway and
call it experimental to start with, or we could get it right all
the
way
On 08.03.12 19:24:00, Cong Ma wrote:
Hi,
Imported library has scope in the directory in which it is created and
below.
If I want to use this library in parent scope, what should I do?
Add the imported library in the top-level cmake file, not a
subdirectory.
Andreas
--
Powered by
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 580171185bac5d23f34f0658b3740973818989b1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 142facc6dd73c3abcf808d598272ccd4bf235463 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 9cdd9896670b54f23ca697eb2f81bc740f880f40 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 9f6c38253a29288a7f8479d43e7c87fd3d958e79 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via da43d8fa8d96f5bb4363b3fd093af97c8735c432 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via fa0f0654262cd74824558c425083e22f091702e0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 36ce6e01f8a1e7f2bdb5604c7776a4a91fa36400 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0127ecdc7de6d26e9c6d2ab09fa82c0d2365e5a1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via aa9a2412888af4457bf330e4c1c72a24879630f2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0171b71ad69350b193bbc7d22dfa55f689689170 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 1abdfd64cedc84ab18c8f57b2d317e3a23cd35aa (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via c7bdef5b48fe74f92d75f538e702257e7de1a998 (commit)
from
40 matches
Mail list logo
