[CMake] CMake toolchain file for multiarch environment (Debian 8)

2015-07-01 Thread Yegor Yefremov
I'm trying to construct a suitable toolchain for CMake 3.0.2. I took Buildroot's toochain.cmake and trying to tweak it: set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR armv7l) # specify the cross compiler SET(CMAKE_C_COMPILER "/usr/bin/arm-linux-gnueabihf-gcc") SET(CMAKE_CXX_COMPILER "/

[CMake] How to find libraries with custom folder structure

2015-07-01 Thread Benedikt Führer
Hi, my jpeg-6b is located in the following folder structure: \libs --\jpeg-6b \include \lib --\x64 \debug \release How can I find the needed files here? The standard FindJPEG in the CMake folder seems to expect a different folder structure and so doesn't find all c

[CMake] Problems loading and using external library

2015-07-01 Thread Gagnon, Joseph - 0553 - MITLL
Let me describe the situation a little. I have a small C++ project with the source files distributed within a small directory hierarchy. I am using JetBrains CLion as the development IDE on a Linux (CentOS 6.6) platform. CLion bundles CMake 3.2.2 in its distribution. I have successfully built th

[CMake] warn if features used that require >cmake-x.y

2015-07-01 Thread Nicolas Bock
Hi, is there a way to get CMake to warn if a feature is used that requires a cmake version greater than some version x.y? Thanks, nick -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services

Re: [CMake] How to find libraries with custom folder structure

2015-07-01 Thread Stuermer, Michael SP/HZA-ZSEP
Did you add the directory where your find script is in to the CMAKE_MODULE_PATH? To verify your script is called, just add a "message("executing my module")" or so on top of your script, this always works very well for me when I'm not sure. See here for more info about the CMAKE_MODULE_PATH: ht

Re: [CMake] warn if features used that require >cmake-x.y

2015-07-01 Thread Stuermer, Michael SP/HZA-ZSEP
Have a look at cmake_minimum_required() and cmake_policy(). I think with these both it should be possible to verify you are using a cmake version that provides all features which are required by your project. See here: http://www.cmake.org/cmake/help/v3.3/command/cmake_minimum_required.html?#co