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
