Re: [CMake] Clang on Cygwin don't build 'dll.a'

Thomas Nilsson skrev: I'm trying to build a CMake project using clang instead of gcc. The project is cross-platform and builds cleanly on Cygwin with gcc. With Clang it says: [ 33%] Built target X make[4]: *** No rule to make target 'X.dll.a', needed by 'X.exe'. Stop.

[CMake] Clang on Cygwin don't build 'dll.a'

I'm trying to build a CMake project using clang instead of gcc. The project is cross-platform and builds cleanly on Cygwin with gcc. With Clang it says: [ 33%] Built target X make[4]: *** No rule to make target 'X.dll.a', needed by 'X.exe'. Stop. CMakeFiles/Makefile2:1140: recipe for target 't

Re: [CMake] CMP0054 and CMake Modules

Sorry, this turned out kind of brief, it was posted in context in Nabble. I'm seeing this on Cygwin. /Thomas thoni56 21 september 2015 09:37 I can't find a bug report on this. Is there one? Surely Cmake distributed modules should not generate this type of warning

[CMake] CMAKE__COMPILER_ID not set on Darwin

I was looking for a way to identify the compiler as clang to know if I should pass it a clang specific flag ("-x c++"). On Darwin default compiler is Clang used through /usr/bin/cc and and /usr/bin/c++. The identification is clearly signaled as "Clang 4.1.0" but CMAKE_CXX_COMPILER_ID is not set

[CMake] Building multiple binaries from same source into one package

t purposes (Makefile which loops over all build directories...). But when it comes to packaging it necessarily creates separate packages. Of course it would be possible to script a merge of them, but that feels.. well, cumbersome. Any suggestions? Is there something I'm missing? I'

Re: [CMake] Cpack not packaging anything

Eric Noulard skrev 2012-11-26 20:12: 2012/11/26 Thomas Nilsson : And I've fixed that, so now it actually packages the correct files. But, next question ;-) Now that I am using a relative (to CMAKE_INSTALL_PREFIX) installation scheme, I'd also like to have my TGZ/TZ/ZIP package to

Re: [CMake] Cpack not packaging anything

Eric Noulard skrev 2012-11-26 19:43: But my real problem is then that I can't get CPack to work without CPACK_SET_DESTDIR. My (inherited) CMakeList.txt:s does specify set(CMAKE_INSTALL_PREFIX /usr/local) but also things like install(... DESTINATION ${BIN_INSTALL_DIR} ...) s

Re: [CMake] Cpack not packaging anything

Eric Noulard skrev 2012-11-26 17:22: 2012/11/26 Thomas Nilsson : Found this: http://www.cmake.org/pipermail/cmake/2008-July/022958.html CPack can't handle absolute install paths (like /usr/local/include) unless CPACK_SET_DESTDIR is set, then it installs in the specified location and pick

Re: [CMake] Cpack not packaging anything

it runs for CPack, but add the > "--debug" and "--verbose" flags to see if that tells you what's going > wrong... > > > HTH, > David > > > On Mon, Nov 26, 2012 at 10:01 AM, Thomas Nilsson > wrote: >> I have a project with multiple su

[CMake] Cpack not packaging anything

I have a project with multiple subdirectories and installs. I'm trying to get it to package the targets using CPack, but nothing gets included in the .tgz when I "make package". There is an install_manifest.txt generated which lists the correct files, but the .tgz is empty. So it seems that CPa

[CMake] Using cmake built dll:s in build tree

On DLL platforms (Windows and Cygwin) shared libraries are found through the PATH and not in some .../lib directory. (There the link stubs are kept.) If I build a shared library in one part of my build tree how can I make sure that this is the DLL that will be loaded when I run an executable fro

[CMake] Actual name of a library

In Cmake scripts names of libraries are used without platform specific pre- and suffixes. Is there a way to convert such a name to the actual filename on the current platform? I need this as an argument to a command in my Ctests... /Thomas -- Powered by www.kitware.com Visit other Kitware op

[CMake] Cmake on Cgwin and WIN32 (actually cmake_minimum_required)

Cmake no longer defines WIN32 on Cygwin. That's alright. However, in the message you get when ccmake-ing it says: "or set the minimum required version of CMake to 2.8.4 or higher" I added cmake_minimum_required(VERSION 2.8.4) but the message still appears. Am I miss-interpreting the

[CMake] Cygwin-build missing ccmake?

I upgraded my cygwin (including cmake) and found that there was no ccmake (that I could find?). Is there and I'm not seeing it? Or if there isn't, was that intentional, and do I have to do anything to get it back? Thomas Nilsson, CTO, Agile Mentor Responsive Development Technolog