Re: [CMake] CMake keeps on referencing an uninstalled Qt

2015-10-12 Thread Laura Médioni
On 10/09/2015 06:48 PM, John Drescher wrote: On Fri, Oct 9, 2015 at 9:53 AM, Laura Médioni wrote: Hi, I am facing a problem with CMake 3.4 under Windows. My CMake project is using Qt. Recently I uninstalled Qt and reinstalled it. Since then, the previous Qt install keeps on appearing in the CM

Re: [CMake] CMake keeps on referencing an uninstalled Qt

2015-10-12 Thread Christian Ehrlicher
Hi,   Did you really recreated (deleted) your CMakeCache.txt after changing your Qt installation? Or at least removed all references to Qt5 in the CMakeCache.txt (e.g. with cmake-gui)?   Christian   Von: "Laura Médioni" Betreff: Re: [CMake] CMake keeps on referencing an uninstalled Qt On 1

Re: [CMake] CMake keeps on referencing an uninstalled Qt

2015-10-12 Thread Laura Médioni
Hi, Yes, I deleted the CMakeCache.txt after changing the Qt installation. Since I still had the same problem, I also tried removing all the cmake generated files. I have a code directory, and a directory where I generate the build. - I removed all the content of this build directory - I opened

[CMake] CMAKE__COMPILER has disappeared?

2015-10-12 Thread Michi Henning
When using ccmake (cmake-curses-gui), I used to easily be able to switch between clang and gcc by hitting "t" and changing the CMAKE_CXX_COMPILER variable to "c++" or "clang++" as appropriate. Doing this would also automatically adjust the path to point at ccache (if ccache is installed). Now,

[CMake] CMAKE_BUILD_TYPE and exact control of compiler options

2015-10-12 Thread René J . V . Bertin
Hello, I'm using cmake in conjunction with a packaging/distribution system that aims to control the compiler and linker flags, a priori via the usual environment variables. (We're talking about MacPorts.) Using one of the CMAKE_BUILD_TYPE presets, the value of those env. variables appears at

Re: [CMake] CMAKE_BUILD_TYPE and exact control of compiler options

2015-10-12 Thread René J . V . Bertin
René J. V. Bertin wrote: Similarly, is there a way to set preprocessor variables (cf. https://cmake.org/Bug/view.php?id=12928 which has been silent for a long time)? One could do -DINCLUDE_DIRECTORIES=${CPPFLAGS}, but that may lead to unexpected results if CPPFLAGS contains something other than

Re: [CMake] CMAKE_BUILD_TYPE and exact control of compiler options

2015-10-12 Thread Andreas Pakulat
Hi, On Mon, Oct 12, 2015 at 10:39 AM, René J. V. wrote: > Hello, > > I'm using cmake in conjunction with a packaging/distribution system that > aims to > control the compiler and linker flags, a priori via the usual environment > variables. (We're talking about MacPorts.) > > Using one of the CM

Re: [CMake] CMAKE_BUILD_TYPE and exact control of compiler options

2015-10-12 Thread René J . V . Bertin
Andreas Pakulat wrote: > No this is not possible in general. A CMakeLists.txt file can always just > set their own compiler/linker flags. Which would require patching each and every one of them, which isn't exactly desirable. >> - Out of curiosity, what's special about the CMAKE_BUILD_TYPE=Deb

[CMake] Creating relocatable packages

2015-10-12 Thread Zac Bergquist
Hello, I'm trying to fix a project so that its output is relocatable. The project is a library that itself depends on libpcap. My goal is to be able to import the library into my CMake application and have CMake automatically link libpcap with it. I'm using a toolchain file that invokes an ARM

[CMake] qt[45]_add_resources: how to use properly with a build time generated qrc file

2015-10-12 Thread Richard Öhlinger
Hi! I've already posted the issue to the Qt bug tracker but was referred to you: https://bugreports.qt.io/browse/QTBUG-36959 I use the Qt5CoreMacros.cmake shiped with Qt5, but as far as I know QT5_ADD_RESOURCES is merely the same as your QT4_ADD_RESOURCE macro. I've already got an custom_targe

[CMake] Cpack components' archive names

2015-10-12 Thread Tomasz Długosz
Hi All, I'm struggling to set custom names for cpack's components' archive names. I call cpack_add_component(): foreach(COMPONENT_NAME ${CPACK_COMPONENTS_ALL}) if (CMAKE_BUILD_TYPE STREQUAL "Debug") cpack_add_component(${COMPONENT_NAME} ARCHIVE_FILE ${PROJECT_NAME}-${COMPONENT_NAME}-

Re: [CMake] FindCUDA discard any previous value of CUDA_USE_STATIC_CUDA_RUNTIME

2015-10-12 Thread James Bigler
Whether you can use the static runtime is based on the toolkit found, so if you change the toolkit (checked with the CUDA_TOOLKIT_ROOT_DIR_INTERNAL variable) we need to reset all dependent values. I don't see a clean way to get this to work in the way you want. The script can't tell the differenc

[CMake] cmake_check_build_system is causing a rebuild at "make install"

2015-10-12 Thread JR Cary
In our use of cmake on a particular project, we noticed that after building the project, upon invoking "make install", the build starts all over again. Hence we are building the project twice. It seems that this is occurring because nearly everything depends on the target, cmake_check_build_syst

[CMake] Specify compiler flags as list?

2015-10-12 Thread Matthew S Wallace
Consider the following CMakeLists.txt (hello.cpp is some standard hello world program) cmake_minimum_required (VERSION 2.6) project(HelloWorld) add_executable(hello hello.cpp) set(WARNING_FLAGS -Wno-char-subscripts -Wno-unused-local-typedefs) #set(WARNING_FLAGS "-Wno-char-subscripts -Wno-unused-l

Re: [CMake] Specify compiler flags as list?

2015-10-12 Thread Dan Kegel
On Mon, Oct 12, 2015 at 8:22 PM, Matthew S Wallace wrote: > Consider the following CMakeLists.txt (hello.cpp is some standard hello world > program) > > cmake_minimum_required (VERSION 2.6) > project(HelloWorld) > add_executable(hello hello.cpp) > set(WARNING_FLAGS -Wno-char-subscripts -Wno-unuse