Re: [CMake] find_library questions

find_library(THELIB NAMES thelibrary.${CMAKE_SHARED_LIBRARY_SUFFIX}) CMAKE_SHARED_LIBRARY_SUFFIX includes the "." though -- so take the "." out of the above line. On Wed, Aug 4, 2010 at 3:53 PM, Alexander Neundorf wrote: > On Wednesday 04 August 2010, Dennis Schridde wrote: > > On Wednesd

Re: [CMake] find_library questions

On Wednesday 04 August 2010, Dennis Schridde wrote: > On Wednesday 04 August 2010 10:03:55 Denis Scherbakov wrote: > > >> 1) Is it > > possible to > > > retrieve the path where find_library found the library? > > E.g. so I can setup > > > ..._LIBRARY_DIR correctly. > > > > Yes, see > > GET_FILENAME

Re: [CMake] Double linking / linking static libraries

On Wednesday 04 August 2010 14:37:03 Eric Noulard wrote: > 2010/8/4 Dennis Schridde : > > Otherwise I will suggest an update to our admins. (Is > > cmake-2.8 available for Fedora 12?) > > Official F12 repo contains 2.6.4 > download.fedora.redhat.com/pub/fedora/linux/updates/12/i386/cmake-2.6.4-5.f

Re: [CMake] Dependencies on imported libraries

On Sunday 01 August 2010 20:50:05 Dennis Schridde wrote: > I just notice that this command does not do what I expected it to do: > > set_property(TARGET MyLib PROPERTY IMPORTED_LOCATION > "${MYLIB_DIR}/build") > > Apparently it sets the path to the *file* that is > MyLib, not to the directory it

Re: [CMake] Misleading error message when enforcing version from foo-config-version.cmake

On 08/04/2010 11:30 AM, Brad King wrote: >> find_package(Foo 6.6.6 REQUIRED NO_MODULE) >> >> and 6.6.6 is a non-valid version (i.e., PACKAGE_VERSION_COMPATIBLE is >> set to FALSE in foo-config-version.cmake), then I get the error message >> that foo-config.cmake is not found, instead of something r

Re: [CMake] Misleading error message when enforcing version from foo-config-version.cmake

On 08/04/2010 11:03 AM, Adolfo Rodríguez Tsouroukdissian wrote: > The foo-config.cmake file is located OK, and: > > find_package(Foo REQUIRED NO_MODULE) > > works as expected. Sorry, I mis-read your message. The find_package call example clears it up. > Now, if I do: > > find_package(Foo 6.6.

Re: [CMake] Double linking / linking static libraries

FindQt4.cmake has been fixed so it doesn't potentially introduce this double linking problem. If you can upgrade, 2.8 would help you. Clint On Aug 4, 2010, at 2:51 AM, Dennis Schridde wrote: > I searched some more and found a trigger for this > behaviour: > > -- > PROJECT(test) > cmake_mi

Re: [CMake] Misleading error message when enforcing version from foo-config-version.cmake

2010/8/4 Brad King > On 08/04/2010 10:25 AM, Adolfo Rodríguez Tsouroukdissian wrote: > > I'm writing a package config file foo-config.cmake, and I'm providing > > version checking via the foo-config-version.cmake. Everything works > > fine, but I've noticed that when version checking fails, the r

Re: [CMake] eliminating -blibpath on AIX

Patch Modules/Platform/AIX.cmake ? >-Original Message- >From: Dave Semeraro [mailto:semer...@ncsa.illinois.edu] >Sent: woensdag 4 augustus 2010 16:42 >To: Verweij, Arjen >Subject: Re: [CMake] eliminating -blibpath on AIX > > >Arjen and Denis, Neither suggestion worked. There seems to be no

Re: [CMake] Misleading error message when enforcing version from foo-config-version.cmake

On 08/04/2010 10:25 AM, Adolfo Rodríguez Tsouroukdissian wrote: > I'm writing a package config file foo-config.cmake, and I'm providing > version checking via the foo-config-version.cmake. Everything works > fine, but I've noticed that when version checking fails, the reported > error message is un

Re: [CMake] eliminating -blibpath on AIX

On 08/04/2010 09:57 AM, Dave Semeraro wrote: > I am building projects on an AIX system and I want the contents of the > link.txt file to not include the -blibpath information at the end. I have > tried all combinations of the CMAKE_SKIP_RPATH and other rpath related > commands and can not get ri

[CMake] Misleading error message when enforcing version from foo-config-version.cmake

Hi all, I'm writing a package config file foo-config.cmake, and I'm providing version checking via the foo-config-version.cmake. Everything works fine, but I've noticed that when version checking fails, the reported error message is uninformative and misleading. It states: Could not find module

Re: [CMake] eliminating -blibpath on AIX

SKIP_BUILD_RPATH ? >-Original Message- >From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf >Of Dave Semeraro >Sent: woensdag 4 augustus 2010 15:58 >To: cmake@cmake.org >Subject: [CMake] eliminating -blibpath on AIX > > >Hello, > >I am building projects on an AIX syste

[CMake] eliminating -blibpath on AIX

Hello, I am building projects on an AIX system and I want the contents of the link.txt file to not include the -blibpath information at the end. I have tried all combinations of the CMAKE_SKIP_RPATH and other rpath related commands and can not get rid of it. I have read the rpath info on the w

[CMake] linking large lib on windows 64 bit

Hi, I'm trying to link my project on Windows. Part of the task is constructing a big archive. Relevant compilers: Intel C/C++, Intel Fortran, Microsoft VS 2005 SE SP1. Apparently the link line is too long (expanded command line lib bla too long). I have attempted to circumvent it with: # crea

Re: [CMake] Double linking / linking static libraries

2010/8/4 Dennis Schridde : > > I am > using Fedora release 12 and cmake version 2.6-patch 4. > The issue is not > reproducible on Gentoo/Linux and cmake version 2.8.1. > > Is cmake-2.6 still being maintained? I don't think so. I think Bill told that 2.6.4 was the last release for 2.6.x. > Otherwi

Re: [CMake] Can cmake be used to build WDK driver applications?

On 8/4/10 4:16 AM, Mr Shore wrote: Hi all, I'm going to develop a WDK driver , not sure whether cmake can help simplify the makefiles this time? Thanks! Should be doable, though I haven't tried it. You'll need to find or create find_

[CMake] Can cmake be used to build WDK driver applications?

Hi all, I'm going to develop a WDKdriver , not sure whether cmake can help simplify the makefiles this time? Thanks! ___ Powered by www.kitware.com Visit other Kitware open-source projects at htt

Re: [CMake] Double linking / linking static libraries

I searched some more and found a trigger for this behaviour: -- PROJECT(test) cmake_minimum_required(VERSION 2.6) find_package(Qt4 REQUIRED) include(${QT_USE_FILE}) set(Boost_ADDITIONAL_VERSIONS 1.38 1.39 1.40 1.41 1.42) find_package(Boost REQUIRED COMPONENTS thread) find_package(GLU REQUIR

Re: [CMake] find_library questions

On Wednesday 04 August 2010 10:03:55 Denis Scherbakov wrote: > >> 1) Is it possible to > > retrieve the path where find_library found the library? E.g. so I can setup > ..._LIBRARY_DIR correctly. > > Yes, see GET_FILENAME_COMPONENT. > > 2) Is it possible to disable the "lib" prefix > that find_l

Re: [CMake] find_library questions

>> 1) Is it possible to retrieve the path where find_library found the library? E.g. so I can setup ..._LIBRARY_DIR correctly. Yes, see GET_FILENAME_COMPONENT. 2) Is it possible to disable the "lib" prefix that find_library always seems to prepend when searching? I have a library that is called "

[CMake] find_library questions

Hello! I have two questions concerning find_library: 1) Is it possible to retrieve the path where find_library found the library? E.g. so I can setup ..._LIBRARY_DIR correctly. 2) Is it possible to disable the "lib" prefix that find_library always seems to prepend when searching? I have a librar

Re: [CMake] Double linking / linking static libraries

On Wednesday 04 August 2010 09:14:29 Ryan Pavlik wrote: > On 8/4/10 2:06 AM, Denis Scherbakov wrote: > >>> * I also set link_directories to paths containing the > > > > libraries. > > > > This is wrong. LINK_DIRECTORIES should be a list of directories, where > > libraries might be located, but

Re: [CMake] Double linking / linking static libraries

On Wednesday 04 August 2010 09:06:06 Denis Scherbakov wrote: > >> * I also set link_directories to paths containing the libraries. > > This is wrong. LINK_DIRECTORIES should be a list of directories, where > libraries might be located, but not the libraries itself. Er, sorry, I meant to paths to d

Re: [CMake] Double linking / linking static libraries

On 8/4/10 2:06 AM, Denis Scherbakov wrote: * I also set link_directories to paths containing the libraries. This is wrong. LINK_DIRECTORIES should be a list of directories, where libraries might be located, but not the libraries itself. Or better yet, skip the link_directories command and us

Re: [CMake] Double linking / linking static libraries

>> * I also set link_directories to paths containing the libraries. This is wrong. LINK_DIRECTORIES should be a list of directories, where libraries might be located, but not the libraries itself. ___ Powered by www.kitware.com Visit other Ki