How does CTest recognize build errors ?
I'm using utility which compile .xml file into .bin, it has output like
this:
Configuration compilator version 2.10
12:09:41: Compiling:
/home/dvorakm/trunk/modest.src/_st/ciernant/cs/cfg.lin.1oo1.xml to
In CMake/Source/CTest/cmCTestBuildHandler.cxx, the line from the build
output has to match one of the regular expressions in cmCTestErrorMatches
*and* not match any of the regular expressions in cmCTestErrorExceptions.
I do not see at first glance why those lines would be reported as an error,
One of the optional steps in generating OSX bundles involves mounting a
temporary disk image so a flag can be set to enable custom icons. Until now
the CPack bundle generator has been using
${CPACK_TOPLEVEL_DIRECTORY}/mnt
as the mountpoint for this operation, which works fine until you stumble
Hi,
This is related more to mpi than to the bug.
Why don't you pass the mpi versionof the compilers to cmake as C/CXX/Fortran?
In this way you are sure that you link with the correct flags.
In my experience for performance reasons you may use some exotic flags when you
compile the mpilibs.
As
We have a shell script that computes the list of libraries that shall
appear on the link comand for every executable. The command looks like
this:
g++ ...flags... object-files... -o myexe `/path/to/script arg1 arg2`
Trying to replicate this with CMake is difficult. My first try was to
put the
Óscar Fuentes [EMAIL PROTECTED] writes:
[snip]
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
--
Oscar
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Óscar Fuentes wrote:
Óscar Fuentes [EMAIL PROTECTED] writes:
[snip]
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config script.
Bill Hoffman [EMAIL PROTECTED]
writes:
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config script. The way to do this is to use
Bill Hoffman [EMAIL PROTECTED]
writes:
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config script. The way to do this is to use
On Aug 11, 2008, at 8:33 PM, Óscar Fuentes wrote:
Bill Hoffman [EMAIL PROTECTED]
writes:
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
This is in general a non-portable way to write cmake files, and is
not
guaranteed to work in any version of CMake. This is the same
Óscar Fuentes wrote:
Bill Hoffman [EMAIL PROTECTED]
writes:
Solved:
target_link_libraries(myexe `/path/to/script arg1 arg2`)
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config script. The way
Mike Jackson [EMAIL PROTECTED] writes:
Just out of curiosity..
Is the dependency tracking in CMake not adequate enough for your
project?
No, see below.
If CMake is used as intended you should not have to manually
figure out what libraries are needed, CMake should be able to do that
for
Bill Hoffman [EMAIL PROTECTED]
writes:
I just realized another reason why your proposal is not adequate: the
libraries and the script must be built before the executable, so, at
cmake time, the libraries and the script does not exists.
I know this is not portable, but it is intended for
13 matches
Mail list logo
