[cmake-developers] CMake and CPack automated testing

Hi, I was looking at CMake automated tests and did not quite understand how they are intended to be written. Do they only test for e.g. if CPack executes without errors or do they check generated files content (e.g. diff or call for e.g. rpm -qi some_pkg.rpm and then diff the output)? I'm not

Re: [cmake-developers] CMake and CPack automated testing

2014-10-15 9:30 GMT+02:00 Domen Vrankar domen.vran...@gmail.com: Hi, I was looking at CMake automated tests and did not quite understand how they are intended to be written. Do they only test for e.g. if CPack executes without errors or do they check generated files content (e.g. diff or

[cmake-developers] FindBoost.cmake cannot find some libraries when cross-compiling

Hello CMake developers, I have a cross-compiled version of Boost and some other libraries under ~/my-project/CrossThirdPartyPrefix. I invoke CMake with a CMAKE_TOOLCHAIN_FILE and also I sets CMAKE_FIND_ROOT_PATH to the directory where my cross-compiled Boost is installed. cmake

Re: [cmake-developers] FindBoost.cmake cannot find some libraries when cross-compiling

Can you post your toolchain file as well? Does it set any of the CMAKE_FIND_ROOT_PATHG_MODE_{INCLUDE,PROGRAM,LIBRARY,PACKAGE} variables to anything? - Chuck On Wed, Oct 15, 2014 at 10:04 AM, Guillaume Papin guillaume.pa...@parrot.com wrote: Hello CMake developers, I have a cross-compiled

Re: [cmake-developers] FindBoost.cmake cannot find some libraries when cross-compiling

Yes I'm setting these variables. See my toolchain configuration below: cmake_minimum_required(VERSION 3.0) # CMAKE_SYSROOT set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR armv7l) set(LINARO_PACKAGE_ROOT /opt/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/) set(CMAKE_SYSROOT

Re: [CMake] Specifying different compilers for subsets of a project

Hi George, You could (ab)use the assembler plugin system for that. Define your own CMake-ASM-BGQ*.cmake files and use the assembler to compile the sources. Here's how I did this a couple of years ago for the BG/P. In the CMakeLists.txt file for the files that need to be compiled with the BG/P

Re: [CMake] 2 libs stuck together !

Hi, It would be a lot easier to help you if you tried to minimize the CMakeLists.txt file before posting it to the list. The file as you posted it contains many unrelated stuff and even commented-out lines. Not wanting to look at the whole thing as it is, my advice to you is to search for the

[CMake] [CPack] RPM generator and directory symlink

Hi, I am trying to package a hierarchy with the following feature: and subdir-version does indeed exist in that lib directory. CPack create a specs featuring but then rpmbuild chokes on it with an error: not a directory: /usr/local/lib/subdir. The %dir should not be there, should it? This

Re: [CMake] [CPack] RPM generator and directory symlink

Just to make it crystal clear, subdir-version is a directory! - -- Luc J. Bourhis -- View this message in context: http://cmake.3232098.n2.nabble.com/CPack-RPM-generator-and-directory-symlink-tp7588751p7588752.html Sent from the CMake mailing list archive at Nabble.com. -- Powered by

[CMake] [CPack] RPM generator and directory symlink

Hi, I am trying to package a hierarchy with the following feature: ~ cd ROOT/usr/local/lib ~ ls -l subdir subdir - subdir-version and subdir-version does indeed exist in that lib directory. CPack create a specs featuring %dir /usr/local/lib/subdir but then rpmbuild chokes on it with an

Re: [CMake] [CPack] RPM generator and directory symlink

According to the answer to this bug report https://bugzilla.redhat.com/show_bug.cgi?id=1005529 , rpmbuild changed the way it deals with when foo or bar are actually symlinks. So it looks like CPack 2.8.12 has not been changed accordingly. This looks like bug report material, doesn't it?

Re: [CMake] [CPack] RPM generator and directory symlink

Hi, I'm assuming that you used something like: install(CODE EXECUTE_PROCESS(COMMAND ln -sf ${SOME_PATH}/subdir-version subdir WORKING_DIRECTORY ${LOCATION_WHERE_CPackRPM_IS_PACKAGING_YOUR_FILES} ) COMPONENT bin) in your CMakeLists.txt Currently CPackRPM doesn't

Re: [CMake] [CPack] RPM generator and directory symlink

Thanks for your help! Domen Vrankar wrote I'm assuming that you used something like: install(CODE EXECUTE_PROCESS(COMMAND ln -sf ${SOME_PATH}/subdir-version subdir WORKING_DIRECTORY ${LOCATION_WHERE_CPackRPM_IS_PACKAGING_YOUR_FILES} ) COMPONENT bin) No, I used

[CMake] INSTALL DIRECTORY patterns highly confusing

The doc could use some more examples. I am having a hard time figuring out how to install a directory tree but exclude files matching .gitignore and Makefile.in. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Re: [CMake] Specifying different compilers for subsets of a project

Hi Marcel, Thanks for your e-mail. I am not sure if your approach wil fully satisfy my use case. I need to compile on both the back-end and front-end. My question really boils down to whether it's possible to use two different compilers for the same language within the same configuration. I was

Re: [CMake] INSTALL DIRECTORY patterns highly confusing

On Wed, Oct 15, 2014 at 6:49 PM, Dan Kegel d...@kegel.com wrote: The doc could use some more examples. I am having a hard time figuring out how to install a directory tree but exclude files matching .gitignore and Makefile.in. This turned out to work for me: install ( DIRECTORY

Re: [CMake] INSTALL DIRECTORY patterns highly confusing

This turned out to work for me: install ( DIRECTORY ${samples_SOURCE_DIR} DESTINATION src PATTERN *.in EXCLUDE PATTERN .gitignore EXCLUDE ) Here's one of my earlier attempts: PATTERN '*.in' EXCLUDE PATTERN 'CMakeLists.txt' EXCLUDE Is it possible that single quotes cause

[Cmake-commits] CMake branch, next, updated. v3.0.2-2071-gd32c4ee

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 d32c4ee7cecd8a27e20e0ebf8c274ce2c1532088 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2073-gf0040c0

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 f0040c0691a6f7ae4a15d434ca67caf53d21b9ea (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2075-g5ed2c9a

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 5ed2c9a236fac1ea9ce747ff0b661e810cfe2ff1 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2077-gac8f6bc

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 ac8f6bc505a27dc8699068dd8a5cb7dc69a5b93a (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2079-g9dbd3a4

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 9dbd3a493b0161893d04737cc3dad30fb8677ab5 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2081-g05ba09f

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 05ba09fc6e695dcbca39289c756f15c7b02f3e5b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.2-2056-g1d86036

20141015) +set(CMake_VERSION_PATCH 20141016) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake