[CMake] Fwd: Questions about CPack Debian generator

I dif forgot thet list... 2010/2/12 Thawan Kooburat ktha...@gmail.com: Hi, I am trying to create a Debian binary package using CMake/CPack and it is quite a nice tool. I understand that CMake/CPack try to rely on external tools as little as possible but there are 2 issues that I encountered

Re: [CMake] Fwd: Questions about CPack Debian generator

Zitat von Eric Noulard eric.noul...@gmail.com: I dif forgot thet list... 2010/2/12 Thawan Kooburat ktha...@gmail.com: Hi, I am trying to create a Debian binary package using CMake/CPack and it is quite a nice tool. I understand that CMake/CPack try to rely on external tools as little as

[CMake] statically linking

Hi, could you please tell me how I can force cmake to link all libraries statically? Thank you very much, Kathrin ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Re: [CMake] statically linking

On 12. Feb, 2010, at 12:46 , burckha...@itis.ethz.ch wrote: Hi, could you please tell me how I can force cmake to link all libraries statically? Thank you very much, Kathrin Just pass the full paths of the static libraries to TARGET_LINK_LIBRARIES. If you're using FIND_PACKAGE to

[CMake] where do libraries go?

Hi I have multiple cmake projects and some of them generate shared libraries. Now to run the program in debug mode, without running the install step, i do ofcourse need the runtime shared libraries when i start the debug. I have the problem that i can't get the path where the library is, so I

Re: [CMake] where do libraries go?

Hi, Mika! I puts all my shared libraries into ${CMAKE_BINARY_DIR}/${CMAKE_BUILD_TYPE}: set_target_properties(target PROPERTIES RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/${CMAKE_BUILD_TYPE} ) It allows to debug without installation With Best Regards, Anatoly. mika.raj...@patria.fi пишет:

[CMake] Problem finding files while cross-compiling

Hi I need to compile a project with a arm cross-compiler. I've used http://www.vtk.org/Wiki/CMake_Cross_Compiling to create my toolchain file= : # system name set(CMAKE_SYSTEM_NAME Linux) # system version (in this case I choosed the kernel version) set(CMAKE_SYSTEM_VERSION 2.6.14-M5) #

Re: [CMake] where do libraries go?

Alternatively, you could use the LOCATION_CONFIG target properties. Ryan On 02/12/2010 07:59 AM, Anatoly Shirokov wrote: Hi, Mika! I puts all my shared libraries into ${CMAKE_BINARY_DIR}/${CMAKE_BUILD_TYPE}: set_target_properties(target PROPERTIES RUNTIME_OUTPUT_DIRECTORY

Re: [CMake] where do libraries go?

On Fri, Feb 12, 2010 at 03:46:06PM +0200, mika.raj...@patria.fi wrote: One solution might be that I set some cmake variables so that all runtime libraries are compiled to the same folder as the exe, but i'd rather keep everything in their own directories. I went down this road -- it's really

Re: [CMake] Examples of CMAKE_INCLUDE_TRANSFORMS or other transform rules?

Yes, I know. The problem is that it's a system header I'm not really permitted to modify. From: Ryan Pavlik rpav...@iastate.edu To: cmake@cmake.org Sent: Thu, February 11, 2010 5:57:58 PM Subject: Re: [CMake] Examples of CMAKE_INCLUDE_TRANSFORMS or other

Re: [CMake] Examples of CMAKE_INCLUDE_TRANSFORMS or other transform rules?

This seems like a bug in CMake, perhaps - file it. I'd think it should convert all discovered paths from headers to cmake-style paths before working with them. Ryan On 02/12/2010 09:39 AM, Jeremy Nicholl wrote: Yes, I know. The problem is that it's a system header I'm not really permitted

Re: [CMake] Solution groups and sub projects.

SOURCE_GROUP only groups files within a single project, not projects. If you have several library or executable projects the solution explorer in VS can get rather crowded. I would love a feature mentioned in the bug http://www.itk.org/Bug/view.php?id=3796 (thanks for the pointer, Micha) which

Re: [CMake] Questions about CPack Debian generator

Are you suggesting that there is a solution for the file owner permission? I try to search in the mailing list but I could not find it. On Fri, Feb 12, 2010 at 3:13 AM, Eric Noulard eric.noul...@gmail.com wrote: 2010/2/12 Thawan Kooburat ktha...@gmail.com: Hi, I am trying to create a Debian

Re: [CMake] Fwd: Questions about CPack Debian generator

2010/2/12 Hendrik Sattler p...@hendrik-sattler.de: Did you dig the mailing list I think the file owner part has been discussed already. Concerning the dpkg-shlibs may be it's worth a feature request? And may be even a contribution? The code of Deb Generator is in:

Re: [CMake] Questions about CPack Debian generator

2010/2/12 Thawan Kooburat ktha...@gmail.com: Are you suggesting that there is a solution for the file owner permission? I try to search in the mailing list but I could not find it. Look at that thread of discussion: http://www.cmake.org/pipermail/cmake/2009-August/031250.html and in the end

[CMake] shared library linking question

hi all, i am trying to write a cmake build system for an existing project and have some troubles with linking of shared libraries. basically, my directory layout of the targets is the following: common/libcommon.so target1/target1 target2/target2 both target1 and target2 are linked with

Re: [CMake] Bison extra headers

They could be if you want. Just open up a bug ticket with some info on how to reproduce and your bison command line and I'll see what I can do. I'm pretty sure all we would have to do is add position.hh, location.hh and stack.hh as OUTPUTs for the custom command for them to be automatically