Brad King wrote:
Brandon J. Van Every wrote:
I think the result is, quotes and backslashes cannot be reliably escaped
with respect to macro wrappers for ADD_CUSTOM_TARGET. Thus it is not
possible to write a macro that will TRY_COMPILE an arbitrary COMMAND.
So the feature that I w
Brandon J. Van Every wrote:
I cannot find any well-defined point of control for escaping
backslashes or quotes in strings and macros. Different levels of CMake
are consuming them differently. This is preventing COMMAND from being
usable in any kind of portable manner.
I have det
Today I inadvertently formed an unwanted circular chain of library
dependencies with the target_link_libraries command, and as a result CMake
segfaulted.
Here is a simple way you can reproduce this segfault (at least for
cmake-2.4.3 that was built and installed on a Ubuntu Dapper platform).
[EMA
Brad King wrote:
Brandon J. Van Every wrote:
I think the result is, quotes and backslashes cannot be reliably escaped
with respect to macro wrappers for ADD_CUSTOM_TARGET. Thus it is not
possible to write a macro that will TRY_COMPILE an arbitrary COMMAND.
So the feature that I w
Philip Lowman wrote:
> Brad King wrote:
>> If they have the same name as a .h or .cc file there is a bug in CMake
>> 2.4.3 that causes this. The work around is to add the HEADER_FILE_ONLY
>> property with SET_SOURCE_FILES_PROPERTIES. It is fixed in CVS CMake and
>> will be fixed in 2.4.4.
>
> So
Brad King wrote:
The SOURCE_GROUP command just maps source files to folders for projects
in which they are already used. You have to list all the sources
(headers, template files, etc.) in the target. Then use SOURCE_GROUP to
map specific file patterns to specific groups. The generated project
Brandon J. Van Every wrote:
> I think the result is, quotes and backslashes cannot be reliably escaped
> with respect to macro wrappers for ADD_CUSTOM_TARGET. Thus it is not
> possible to write a macro that will TRY_COMPILE an arbitrary COMMAND.
>
> So the feature that I would like, is a TRY_COMM
Brandon J. Van Every wrote:
Brandon J. Van Every wrote:
William A. Hoffman wrote:
At 08:17 AM 7/22/2006, Brad King wrote:
You can create a macro to wrap this all up.
Regardless of the documentation, try-compile and not exec_process is what i
return retVal;
it should be
return !retval,
the imagecomparison returns the opposite result from what you'd expect
if I recall correctly.
JB
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi David,
piping the command line output from
ctest -V -R TestCommonGeomUtils2 gives:
Start processing tests
Test project
Constructing a list of tests
Done constructing a list of tests
Changing directory into
d:/Developer/Releases/Borland/vtkLocalStatic/Common/Testing/Cxx
3/ 3 Testing TestComm
Looks like the test didn't fail:
0Standard0.14
...at least not because of ImageError. The value for the ImageError
measurement is 0. If it failed, it failed because of something else.
Did ctest report that the test failed? What's the output if you run
ctest -V -R TestCommonGeomUtils2?
You'
Enrico Scholz wrote:
> does there exist a way to rename a target 'exe-foo' so that it is
> installed as 'bin/foo' finally?
You can do this at build time before installing. See OUTPUT_NAME in
SET_TARGET_PROPERTIES.
-Brad
___
CMake mailing list
CMake@cma
Brandon J. Van Every wrote:
William A. Hoffman wrote:
At 08:17 AM 7/22/2006, Brad King wrote:
Brandon J. Van Every wrote:
Ok, the CMake 2.4.2 documentation for the projectName version of TRY_COMPILE is only 3 short sentences. IIUYC, you are sayin
Hello,
does there exist a way to rename a target 'exe-foo' so that it is
installed as 'bin/foo' finally?
With cmake-2.4.3, I tried
| install(TARGETS exe-foo
| RUNTIME DESTINATION bin
| RENAME foo)
but this fails with
| INSTALL TARGETS given unknown argument "RENAME".
The background is,
Richard Fuchs wrote:
> Ah, I see the note now. It's not in the section of the cmake book that
> describes the command, but it's in the command index in the back and on
> the web.
> So why does it work with the add_custom_target?
It doesn't AFAIK. The custom rule specified by the custom target is
Ah, I see the note now. It's not in the section of the cmake book that
describes the command, but it's in the command index in the back and on
the web.
So why does it work with the add_custom_target?
Brad King wrote:
>From the documentation of ADD_CUSTOM_COMMAND:
"Note that the PRE_BUILD op
Slava Semushin wrote:
> - I added ENABLE_TESTING() to CMakeLists.txt and ADD_TEST() to
> tests/CMakeLists.txt and my test works. But I see autogenerated
> files with name DartTestfile.txt in src/ also:
>
> [EMAIL PROTECTED] ~/openfm]$ cat src/DartTestfile.txt
> # CMake
Richard Fuchs wrote:
> I've added some logging around each of our libraries that we build, but
> I'm getting an unexpected result. I'm using a custom command with the
> cmake -E echo to print a log out before and after a library is built.
> However, the results are not consistent. When we have c
Filipe Sousa wrote:
> [EMAIL PROTECTED] ~/build/stl $ make scanner.i
> make[1]: *** No rule to make target `cmake_force', needed by
> `CMakeFiles/stl.dir/scanner.i'. Stop.
> make: *** [scanner.i] Error 2
>
> [EMAIL PROTECTED] ~/build/stl $ cmake --version
> cm
I've added some logging around each of our libraries that we build, but
I'm getting an unexpected result. I'm using a custom command with the
cmake -E echo to print a log out before and after a library is built.
However, the results are not consistent. When we have custom targets,
things wor
Hi David,
thanks for your reply.
I have a couple more questions (for anyone) based on
CMake testing of VTK/Examples/Build/vtkMy,
since I seem to be generating image test errors with ctest.
In my root CMakeLists.txt, I added the following to do
hopefully basic testing, without submitting results
The output that goes to the console during a ctest driven execution of
your test will show up amidst the ctest output if you use "-V" when
invoking ctest.
And even if you don't use -V, ctest puts the console output from tests
like this into "${CMAKE_BINARY_DIR}/Testing/Temporary/LastTest*.log"
[EMAIL PROTECTED] ~/build/stl $ make scanner.i
make[1]: *** No rule to make target `cmake_force', needed by
`CMakeFiles/stl.dir/scanner.i'. Stop.
make: *** [scanner.i] Error 2
[EMAIL PROTECTED] ~/build/stl $ cmake --version
cmake version 2.5-20060920
--
Filipe Sousa
sig
Slava Semushin wrote:
> --- Brad King 2006-09-19 10:17:27 -0400
> +++ Slava Semushin 2006-09-20 11:47:40 +0700
>
> BK> In CMake 2.4 CPack is still in beta.
>
> Really beta... =(
>
> [EMAIL PROTECTED] ~]$ cpack
> CPack Error: CPack generator not specified
> terminate called after
24 matches
Mail list logo
