[CMake] cmake / ctest crosscompiling support?

Hello, I was wondering if cmake also supports crosscompiling. And is there any experience running ctest on crosscompiled executables? Best regards, Jeroen Janssen ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] problems detecting a required version of a library

Scott Amort wrote: Hello, I am in the process of converting my C++ library project from autotools to CMake. So far, things are working very well. However, I have come across a strange problem. I have written a cmake module that attempts to detect if ANTLR is installed, by checking

Re: [CMake] targets and dependencies

David Somers wrote: For a cmake project, it it possible to get a list of all its targets; and for the targets to get their dependencies? There is no official interface for this. You could try using get_cmake_property to get the CACHE_VARIABLES property. Look for variables of the form

[CMake] No COMMENT for ADD_CUSTOM_TARGET?

Is there a reason why ADD_CUSTOM_TARGET doesn't support having a COMMENT? -- David Somers SIP: FWD dial **44808449868206; voipuser.org dial 08449868206 PGP Key = 7E613D4E Fingerprint = 53A0 D84B 7F90 F227 2EAB 4FD7 6278 E2A8 7E61 3D4E ___ CMake

RE: [CMake] Compile/install on HPUX on ia64 (Itanium)

Hi, I looked at the CMakeOutput.log as Brad suggested and saw the error message, it suggests putting the +p as an option. That got me past that error, now I am getting: Unsatisfied symbol getmaxx in file /home/khoros/cmake-2.4.2/Source/CursesDialog/form/libcmForm.a[frm_driver .o] ld:

Re: [CMake] problems detecting a required version of a library

Hi Brad, Thanks for the quick response. Brad King wrote: What is the output value of antlr-config --libs? What is the command you are using to store the value in the cache? The output value is: /usr/lib64/libantlr.a on my AMD64 gentoo box. I'm not doing anything specific re: cache, here are

Re: [CMake] problems detecting a required version of a library

Scott Amort wrote: Hi Brad, Thanks for the quick response. Brad King wrote: What is the output value of antlr-config --libs? What is the command you are using to store the value in the cache? The output value is: /usr/lib64/libantlr.a on my AMD64 gentoo box. I'm not doing anything

Re: [CMake] No COMMENT for ADD_CUSTOM_TARGET?

On Wednesday 28 June 2006 19:28, Brad King wrote: David Somers wrote: Is there a reason why ADD_CUSTOM_TARGET doesn't support having a COMMENT? It just hasn't been implemented. Whoever added it to ADD_CUSTOM_COMMAND did not add it to ADD_CUSTOM_TARGET too. Looking at the code it may not

RE: [CMake] Compile/install on HPUX on ia64 (Itanium)

Hi, Success with latest from CVS!!! Both make and make install seems to work, Thanks, I added the option by setting the environment variables before running configure. (At the bash prompt before running configure) export CFLAGS=+p export CXXFLAGS=+p BTW: I had to delete the whole directory in

Re: [CMake] Compile/install on HPUX on ia64 (Itanium)

David Akdikmen wrote: Success with latest from CVS!!! Both make and make install seems to work, Thanks, Great. I added the option by setting the environment variables before running configure. (At the bash prompt before running configure) export CFLAGS=+p export CXXFLAGS=+p What was the

RE: [CMake] Compile/install on HPUX on ia64 (Itanium)

Odd, I'm not sure what's going on. When I cc the file at the command prompt, it doesn't complain about the __attribute__ symbols. It looks like it is complaining about not having a LF at the end of the file? It looks like it thinks __attribute__ is just some function returning int? Does your

RE: [CMake] Compile/install on HPUX on ia64 (Itanium)

My HP does this: Performing C SOURCE FILE Test ATTR_UNUSED_VAR succeded with the following output: gmake -f CMakeFiles/cmTryCompileExec.dir/build.make CMakeFiles/cmTryCompileExec. dir/build gmake[1]: Entering directory `/mnt/kitware/Dashboards/MyTests-HP-UXUB.11.19000-8

Re: [CMake] problems detecting a required version of a library

Hi Brad, Brad King wrote: No, EXEC_PROGRAM and EXECUTE_PROCESS have different policies for capturing the output of a program. It looks like EXEC_PROGRAM automatically strips leading and trailing whitespace from the output, while EXECUTE_PROCESS gives you the real output of the program.