Re: [CMake] Transitive linking

On Fri, Nov 18, 2011 at 5:51 PM, Michael Hertling wrote: > On 11/18/2011 10:03 PM, James Bigler wrote: > > 2011/11/18 Alexander Neundorf > > > >> On Friday 18 November 2011, James Bigler wrote: > >>> I thought CMake knew how to not drag all the dependent libraries once > you > >>> linked an execu

Re: [CMake] VC2010 Express + CMake = fails

On 11/18/2011 6:58 PM, Robert Dailey wrote: Well since this is VC Express, I don't have a "devenv.com " file in my Common7 folder, so I guess that explains it? Shouldn't CMake support VC2010 express? - It does, it is just confused because you have two compilers...

Re: [CMake] Install command incorrectly installing archive libraries

On Fri, 2011-11-18 at 22:49 +0100, Michael Wild wrote: > Sorry, I misread the documentation myself. You need multiple install() > commands, for each configuration one, but after each DESTINATION option > you also need the COMPONENTS option. So, this would be something like this: > > install(TARGET

Re: [CMake] VC2010 Express + CMake = fails

On 11/18/2011 6:10 PM, Robert Dailey wrote: Run Build Command:C:\PROGRA~2\MICROS~2.NET \Common7\IDE\devenv.com CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec Microsoft (R) Development Environment Version 7.10.6030. Looks like it is running VS 7,

Re: [CMake] Transitive linking

On 11/18/2011 10:03 PM, James Bigler wrote: > 2011/11/18 Alexander Neundorf > >> On Friday 18 November 2011, James Bigler wrote: >>> I thought CMake knew how to not drag all the dependent libraries once you >>> linked an executable module. >>> >>> add_library(A STATIC a.cpp) >>> add_library(B SHA

Re: [CMake] VC2010 Express + CMake = fails

Well since this is VC Express, I don't have a "devenv.com" file in my Common7 folder, so I guess that explains it? Shouldn't CMake support VC2010 express? - Robert Dailey On Fri, Nov 18, 2011 at 5:10 PM, Robert Dailey wrote: > When I try to configure my project in CMake 2.8.6 using VC

[CMake] VC2010 Express + CMake = fails

When I try to configure my project in CMake 2.8.6 using VC 2010 Express, I get the following error. Any reason why? Check for working C compiler using: Visual Studio 10 Check for working C compiler using: Visual Studio 10 -- broken CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/

Re: [CMake] [RFC] How to use pkg-config under Windows (... and OSX)?

On Friday 18 November 2011, Alan W. Irwin wrote: > On 2011-11-17 21:43+0100 Hendrik Sattler wrote: > > Am Donnerstag, 17. November 2011, 21:38:20 schrieb Hendrik Sattler: > >> Am Donnerstag, 17. November 2011, 18:26:08 schrieb Alexander Neundorf: > >>> Let's say package Foo (unrelated to KDE, and u

Re: [CMake] [RFC] How to use pkg-config under Windows (... and OSX)?

Am 18.11.2011 02:02, schrieb Alan W. Irwin: > Alex, is it possible your KDE Windows developers who are objecting to > pkg-config tried a version from years ago when it did not have all > these Windows issues sorted out? I suggest you tell them to > investigate again using modern pkg-config. For ex

Re: [CMake] Install command incorrectly installing archive libraries

Sorry, I misread the documentation myself. You need multiple install() commands, for each configuration one, but after each DESTINATION option you also need the COMPONENTS option. So, this would be something like this: install(TARGETS first ARCHIVE DESTINATION lib/release CONFIGURATIONS Release

Re: [CMake] Transitive linking

2011/11/18 Alexander Neundorf > On Friday 18 November 2011, James Bigler wrote: > > I thought CMake knew how to not drag all the dependent libraries once you > > linked an executable module. > > > > add_library(A STATIC a.cpp) > > add_library(B SHARED b.cpp) > > target_link_libraries(B A) > > add

Re: [CMake] Transitive linking

On Friday 18 November 2011, James Bigler wrote: > I thought CMake knew how to not drag all the dependent libraries once you > linked an executable module. > > add_library(A STATIC a.cpp) > add_library(B SHARED b.cpp) > target_link_libraries(B A) > add_library(C SHARED c.cpp) > target_link_librarie

[CMake] Transitive linking

I thought CMake knew how to not drag all the dependent libraries once you linked an executable module. add_library(A STATIC a.cpp) add_library(B SHARED b.cpp) target_link_libraries(B A) add_library(C SHARED c.cpp) target_link_libraries(C B) add_executable(run run.cpp) target_link_libraries(run C)

Re: [CMake] [RFC] How to use pkg-config under Windows (... and OSX)?

On Friday 18 November 2011, Alan W. Irwin wrote: > On 2011-11-17 21:43+0100 Hendrik Sattler wrote: > > Am Donnerstag, 17. November 2011, 21:38:20 schrieb Hendrik Sattler: > >> Am Donnerstag, 17. November 2011, 18:26:08 schrieb Alexander Neundorf: > >>> Let's say package Foo (unrelated to KDE, and u

Re: [CMake] One project, one platform, 2 compilers

Thank you very much for the answers, David and Michael. I am trying to get a QNX compiler to work with CMake. My host comp runs Ubuntu. I did: cmake -G "Unix Makefiles -D CMAKE_C_COMPILER=qcc -D CMAKE_CXX_COMPILER=QCC .. but get dpkg-architecture: warning: Couldn't determine gcc system type, fall

Re: [CMake] Install command incorrectly installing archive libraries

Using the single command will place the release libraries into the lib/release directory when using the -C Release flag with CPack. If I do -C Debug flag with CPack then the PDB files are installed to lib/debug but the libraries are installed to lib/release. Any reason why this single command would

Re: [CMake] Problems with CPack/NSIS and CPACK_NSIS_MUI_FINISHPAGE_RUN

Thanks, >> set(CPACK_NSIS_EXECUTABLES_DIRECTORY ".") This solves the problem. Best Regards Am 18.11.2011 um 13:08 schrieb David Cole : > set(CPACK_NSIS_EXECUTABLES_DIRECTORY ".") -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/ope

Re: [CMake] TCL modules

I posted a patch showing what I did, but it is waiting on the moderators due to it just barely being over the size limit. In a nutshell though. Once a version is specified I would build a variable for the NAME part of the find_* functions that would force the filename with version first in the li

Re: [CMake] TCL modules

On 11/17/2011 05:53 PM, Joe Brandt wrote: > I totally agree with your #2. I was thinking that it would be easier to > try and update the existing ones, rather than create new ones, at least > from the perspective of getting something done more quickly. The main > issue with that is that a new Fin

Re: [CMake] One project, one platform, 2 compilers

On 11/17/2011 05:18 PM, Paul Hansen wrote: > Hi > > I have a project that has to be compiled with two different compilers on > the same computer. > > Can I do that from the same CMakeLists.txt file? What do you mean exactly? (1) Compile the project twice, each time completely with a different c

Re: [CMake] Problems with CPack/NSIS and CPACK_NSIS_MUI_FINISHPAGE_RUN

Actually, that commit just led me to a usage of that variable. The docs were added later. On Fri, Nov 18, 2011 at 7:06 AM, David Cole wrote: > This commit shows the code that fixed the bug, and led me to the docs > for that variable: > >  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bee514

Re: [CMake] Problems with CPack/NSIS and CPACK_NSIS_MUI_FINISHPAGE_RUN

This commit shows the code that fixed the bug, and led me to the docs for that variable: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bee514c3611f7a7b972d9ade14f94c0f25bc001e On Fri, Nov 18, 2011 at 7:04 AM, David Cole wrote: > If you want to run an executable in the "MyProject" direct

Re: [CMake] Problems with CPack/NSIS and CPACK_NSIS_MUI_FINISHPAGE_RUN

If you want to run an executable in the "MyProject" directory instead of the "bin" directory, then set: set(CPACK_NSIS_EXECUTABLES_DIRECTORY "MyProject") If you want to run one in the root installation directory, set: set(CPACK_NSIS_EXECUTABLES_DIRECTORY ".") So I still assert that the