[CMake] Debian packaging auto-dependency bugfix

2012-05-14 Thread Jess Morecroft
Hi all, I experienced problems recently trying to use the CPack DEB packager with components and wanted to share my solution (thanks partly to Eric Noulard). The problem was with dependency generation in the Debian control file using the CPACK_DEBIAN_PACKAGE_SHLIBS flag. Dependencies would be

Re: [CMake] fixup_bundle() doesn't like libglut.3.dylib

2012-05-14 Thread David Cole
Rather than just doing a "fixup_bundle" as an INSTALL(CODE snippet, put it in a separate CMake script, and use install(SCRIPT to execute it. You can configure the script with configure_file if you need to put stuff in it that depends on CMake variables. Then, in your script: # Define the functi

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Robert Dailey
Sorry, I forgot that I already had that code pasted in my original post. Sorry for the duplicate code :) On Mon, May 14, 2012 at 5:17 PM, Robert Dailey wrote: > On Mon, May 14, 2012 at 4:58 PM, Bill Hoffman wrote: >> >> For those we hard coded many of the flags into a table. So, basically >> for

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Robert Dailey
On Mon, May 14, 2012 at 4:58 PM, Bill Hoffman wrote: > > For those we hard coded many of the flags into a table. So, basically for > VS greater than 6, we have a table that maps flags to actual options in the > IDE. There is no special per-compiled support in CMake... :) > > All it knows is that

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Bill Hoffman
On 5/14/2012 5:48 PM, Robert Dailey wrote: I'm seeing this behavior in VS 2003 and VS 2008 as well. Is the same script used by CMake for these generators too? It's working somehow... For those we hard coded many of the flags into a table. So, basically for VS greater than 6, we have a table th

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Robert Dailey
On Mon, May 14, 2012 at 3:45 PM, Bill Hoffman wrote: > On 5/14/2012 2:26 PM, Robert Dailey wrote: > >> No one has anything to say about this? >>CMake seems to do more than just add them as general compiler flags, >>it seems to know exactly which attributes in the VCPROJ XML are >>mappe

Re: [CMake] fixup_bundle() doesn't like libglut.3.dylib

2012-05-14 Thread Joe Ping-Lin Hsiao
Thanks, this is exactly what I need. Just one question. Why the function gp_resolved_file_type_override() cannot be seen if it is implemented in my project's CMakeLists.txt? I have to add it in GetPrerequisite.cmake module, but that's not good. Thanks, Joe On Mon, May 7, 2012 at 11:04 AM, David

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Bill Hoffman
On 5/14/2012 2:26 PM, Robert Dailey wrote: No one has anything to say about this? CMake seems to do more than just add them as general compiler flags, it seems to know exactly which attributes in the VCPROJ XML are mapped to their respective command line alternatives, and uses the

[CMake] error executing example of vtk

2012-05-14 Thread Gonzalo Amadio
Hello everyone, I am trying to execute the vtk example : http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/WriteVTP As the example guide says, I create a folder call test, then inside this folder I put WriteVTP.cxx and the CmakeLists.txt given in the example. I am trying to compile it, and give me this

Re: [CMake] Secret precompiled header support?

2012-05-14 Thread Robert Dailey
No one has anything to say about this? On Wed, May 9, 2012 at 1:32 PM, Robert Dailey wrote: > To my knowledge there are no dedicated target properties or commands that > allow one to easily add precompiled headers support to a target. In my > case, I'm generating for visual studio and I have the

Re: [CMake] Have Visual Studio project name be different than the executable name

2012-05-14 Thread Petr Kmoch
Hi Cristian. There are two ways to go about this, either using OUTPUT_NAME or PROJECT_LABEL. It also depends on what you want the target name in Makefiles to be: (1) add_executable(def) #name of Makefile target and executable will be `def' set_property(TARGET def PROPERTY PROJECT_LABEL "ABC") #na

Re: [CMake] [CPack] Empty package while using component with NSIS on Win64 platform.

2012-05-14 Thread Eric Noulard
2012/5/14 Alexandre Fournier : > Hi Eric, > > I did found my problem, and it is working.  There was a slight difference > between what I posted and what is actually on my script (for confidentiality > issue). OK. > One of my component had 29 chars long, I just reduce the name and it worked.   >

Re: [CMake] [CPack] Empty package while using component with NSIS on Win64 platform.

2012-05-14 Thread Alexandre Fournier
Hi Eric, I did found my problem, and it is working. There was a slight difference between what I posted and what is actually on my script (for confidentiality issue). One of my component had 29 chars long, I just reduce the name and it worked. Probably a window path longuer than 255 chars ..

Re: [CMake] Default value for CMAKE_BUILD_TYPE

2012-05-14 Thread Jean-Christophe Fillion-Robin
Hi Eric, Considering the fact Visual Studio is a multi-configuration system, I don't think using "CMAKE_BUILD_TYPE" is what you want. Indeed, in such case, the build type is know at build time only. See [1] Hth Jc [1] http://www.cmake.org/cmake/help/v2.8.8/cmake.html#variable:CMAKE_CFG_INTDIR

Re: [CMake] Default value for CMAKE_BUILD_TYPE

2012-05-14 Thread pellegrini
On 5/11/2012 5:30 PM, Jean-Christophe Fillion-Robin wrote: Hi Eric, In our different projects, we use an approach similar to this one: # Set a default build type if none was specified if(NOT CMAKE_BUILD_TYPE AND NOT CMAKE_CONFIGURATION_TYPES) message(STATUS "Setting build type to 'Debug' as

Re: [CMake] [CPack] Empty package while using component with NSIS on Win64 platform.

2012-05-14 Thread Alexandre Fournier
The new example is working, I guess I did not have the latest one, that is good news to me. I removed all absolute path from install command : INSTALL(TARGETS triage RUNTIME DESTINATION bin COMPONENT triageApp) I disabled the SET_DESTDIR and remove the command after

Re: [CMake] [CPack] Empty package while using component with NSIS on Win64 platform.

2012-05-14 Thread Eric Noulard
2012/5/14 Alexandre Fournier : > Hello, > > > > I am trying to create a package for our project.  The package contains > several components, one for each application.  I followed the instruction > from the book “Mastering CMake” and the package is created but has no > components.  Our solution runs

[CMake] [CPack] Empty package while using component with NSIS on Win64 platform.

2012-05-14 Thread Alexandre Fournier
Hello, I am trying to create a package for our project. The package contains several components, one for each application. I followed the instruction from the book "Mastering CMake" and the package is created but has no components. Our solution runs entirely on CMake including continuous int

[CMake] Have Visual Studio project name be different than the executable name

2012-05-14 Thread Cristian Cocheci
I want my project name in Visual Studio to be different than the executable name. This is how I currently have it set up: project( ABC ) ... add_executable( def ) When I open the solution, the project name is "def", but I want it to be ABC (with the corresponding ABC.vcproj project file outpu

Re: [CMake] How to use different assemblers in single build?

2012-05-14 Thread Alexey Istomin
>> Thanks! set_source_files_properties works fine! >> It seams last question. Is it possible to place >> CMakeASM-DSPInformation.cmake, CMakeDetermineASM-DSPCompiler.cmake and >> CMakeTestASM-DSPCompiler.cmake files inside the project (without copy to >> system usr\share\cmake-2.8.7\Modules)? In

Re: [CMake] Volunteering to become maintainer of FindLibLZMA.cmake

2012-05-14 Thread Mario Bensi
Hi, The last file with all change requested is correct for you ? Do you think it's possible to integrate it in cmake ? Mario On Thursday, May 10, 2012 09:26:21 AM Mario Bensi wrote: > Hi Eike, > > The new version of FindLibLZMA.cmake all changes > > Mario > > On Wednesday, May 09, 2012 10:00