Re: [CMake] CPack and 7-Zip?

Thanks for the suggestion but still no 'sutable' ZIP program found. I have associated 7-Zip with .zip files (and all other possible extensions .tar .gz .rar and so on.) and added 7-Zip to the system path. But unfortunately CPack was not able to use 7-Zip yet. I used my *old* system again and no

Re: [CMake] CPack Questions and Issues

ne install. Nevertheless I don't know if CMake+CPack support this but it seems doable as custom CMake MACROs set. * When are the Welcome, Description and Readme files used? Don't know. * The NSIS generator ignores most of the variables you'd think it would use, and instead app

Re: [CMake] CPack Questions and Issues

On 5/21/07, Eric Noulard <[EMAIL PROTECTED]> wrote: 2007/5/20, Stuart Herring <[EMAIL PROTECTED]>: > * The NSIS generator ignores most of the variables you'd think it > would use, and instead appears to use the > CPACK_PACKAGE_INSTALL_DIRECTORY variable for everything, including the > name of the

[CMake] CPack and nsis on Linux

Hi all I already wrote this to bug tracker[1], but it didn't gain any attention so far. CPack can currently use nsis for creating Windows installers only on Windows. As nsis is also available on Linux, I see no reason why CPack could not use it to produce Windows installers on Linux. I've made pa

Re: [CMake] CPack and 7-Zip?

On Tuesday 15 May 2007 04:50, Peter Visser wrote: > Thanks for the suggestion but still no 'sutable' ZIP program found. > > I have associated 7-Zip with .zip files (and all other possible extensions > .tar .gz .rar and so on.) and added 7-Zip to the system path. But > unfortunately CPack was not a

Re: [CMake] CPack and 7-Zip?

I just tried the current cvs HEAD, 7zip now works fine in my case. Thanks for the effort! However, the current cvs HEAD seems to ignore my 'STRIP_FILES' rule: SET(CPACK_STRIP_FILES "bin/*.exe") It now strips all files including dll's. This may be a cvs development issue, or perhaps the command

Re: [CMake] CPack and 7-Zip?

On Thursday 14 June 2007 16:11, Peter Visser wrote: > I just tried the current cvs HEAD, 7zip now works fine in my case. > Thanks for the effort! > > However, the current cvs HEAD seems to ignore my 'STRIP_FILES' rule: > > SET(CPACK_STRIP_FILES "bin/*.exe") > > It now strips all files including dl

Re: [CMake] CPack and 7-Zip?

I rather like the current (2.4.6) fine grained approach. In the past I experienced problems (run-time crashes) when stripping dll's, hence not stripping them better suits my specific case. Furtermore, the cvs version complains that it cannot find the archive files (which are not required in the p

Re: [CMake] CPack and 7-Zip?

On Thursday 14 June 2007 16:36, Peter Visser wrote: > I rather like the current (2.4.6) fine grained approach. In the past I > experienced problems (run-time crashes) when stripping dll's, hence not > stripping them better suits my specific case. > > Furtermore, the cvs version complains that it ca

Re: [CMake] CPack and 7-Zip?

Hello Alex, Hereby a minimal testcase, I used the CMakeExample and added some INSTALL/PACK rules. Cheers, Peter. WinXP/MinGW build output: $ cmake -G "MSYS Makefiles" ../. -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: C:/Pro

Re: [CMake] CPack and 7-Zip?

On Friday 15 June 2007 03:04, Peter Visser wrote: > Hello Alex, > > Hereby a minimal testcase, I used the CMakeExample and added some > INSTALL/PACK rules. Thanks. > On 6/14/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote: > > On Thursday 14 June 2007 16:36, Peter Visser wrote: > > > I rather li

Re: [CMake] CPack and 7-Zip?

We'll do something about it. How about adding options to the install() command like STRIP_ALWAYS and STRIP_NEVER ? Do you mean something like this: INSTALL(TARGETS helloworld RUNTIME DESTINATION bin STRIP_ALWAYS LIBRARY DESTINATION lib STRIP_NEVER

Re: [CMake] CPack and 7-Zip?

On Friday 15 June 2007 11:47, Peter Visser wrote: > > We'll do something about it. > > How about adding options to the install() command like STRIP_ALWAYS and > > STRIP_NEVER ? > > Do you mean something like this: > > INSTALL(TARGETS helloworld > RUNTIME DESTINATION bin STRIP_ALWA

Re: [CMake] CPack and 7-Zip?

> INSTALL(TARGETS helloworld > RUNTIME DESTINATION bin STRIP_ALWAYS > LIBRARY DESTINATION lib STRIP_NEVER > ARCHIVE DESTINATION lib STRIP_NEVER >) > > In my case that would work very well. I guess you would do it this way for

Re: [CMake] CPack and 7-Zip?

On Friday 15 June 2007 12:28, Peter Visser wrote: > > > INSTALL(TARGETS helloworld > > > RUNTIME DESTINATION bin STRIP_ALWAYS > > > LIBRARY DESTINATION lib STRIP_NEVER > > > ARCHIVE DESTINATION lib STRIP_NEVER > > >) > > > > > >

Re: [CMake] CPack and 7-Zip?

Please update from cvs. It seems stripping static libs is a bad idea (since it removes their symbol table) and stripping import libs doesn't make sense (since they don't have debug information), so both are now excluded from stripping. Please correct me if I'm wrong. Let me know if stripping t

Re: [CMake] CPack and 7-Zip?

On Monday 18 June 2007 03:58, Peter Visser wrote: > > Please update from cvs. > > > > It seems stripping static libs is a bad idea (since it removes their > > symbol > > table) and stripping import libs doesn't make sense (since they don't > > have debug information), so both are now excluded from

[CMake] [CPACK] one project, many packages ?

Hi again, Is it possible to create many packages from one project ? If my project have many subproject for example ? Regards, -Mehdi ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] CPack TGZ Generator and symlinks

Hi all, I currenlty have something like this to create and install a symlink as part of my application: ADD_CUSTOM_COMMAND(TARGET target POST_BUILD COMMAND ln -s -f foo bar DEPENDS foo VERBATIM) INSTALL_FILES("/" FILES bar ) I'm also using CPack

[CMake] CPack for making .deb files?

Hi guys, I need my CMake-based project to produce Debian packages in the near-term, and RPMs probably a few months from now. I've already worked out how to create .deb files (using a traditional Makefile and the dpkg-deb and lintian programs). But then I look at CPack, which appears to be inten

[CMake] CPack for making .deb files?

2007/7/30, Christian Convey <[EMAIL PROTECTED]>: > > Now that I know CPack 2.6 is supposed to produce .deb files, I've > decided not to go crazy trying to produce a version of DpkgDeb that > I'm satisfied with. Where this information comes from? I'm interested in this and I monitor the list messag

Re: [CMake] [CPack] debian binary package

On 8/14/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: > Hi, > > As some people have already noticed there has been some work done in > CPack to support deb package. After my initial draft Alex finished up > the implementation today. > > I believe the code is ready for more testing now. > >

Re: [CMake] [CPack] debian binary package

On 8/14/07, Tristan Carel <[EMAIL PROTECTED]> wrote: > I will make more serious test with `advanced' options: > DEBIAN_PACKAGE_DEPENDS, stuff like that... If anyone has any experience with this, he should speak now or hold his peace forever. As far as I understand to automate the process I need t

Re: [CMake] [CPack] debian binary package

Am Dienstag 14 August 2007 15:44 schrieb Mathieu Malaterre: > On 8/14/07, Tristan Carel <[EMAIL PROTECTED]> wrote: > > I will make more serious test with `advanced' options: > > DEBIAN_PACKAGE_DEPENDS, stuff like that... > > If anyone has any experience with this, he should speak now or hold > his

Re: [CMake] [CPack] debian binary package

On Wednesday 15 August 2007 04:16, Hendrik Sattler wrote: > Am Dienstag 14 August 2007 15:44 schrieb Mathieu Malaterre: > > On 8/14/07, Tristan Carel <[EMAIL PROTECTED]> wrote: > > > I will make more serious test with `advanced' options: > > > DEBIAN_PACKAGE_DEPENDS, stuff like that... > > > > If a

Re: [CMake] [CPack] debian binary package

On 8/14/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote: > On 8/14/07, Tristan Carel <[EMAIL PROTECTED]> wrote: > > I will make more serious test with `advanced' options: > > DEBIAN_PACKAGE_DEPENDS, stuff like that... > > If anyone has any experience with this, he should speak now or hold > his pea

Re: [CMake] Re: CMake, CPack, RPM

2007/10/11, kent williams <[EMAIL PROTECTED]>: > Thanks for your prompt reply. To some extent you're answering > questions that come from me being an RPM newbie. > > My problem with the Source RPM generation is that it requires that my > system -- the one building the source RPM, doesn't have CMak

Re: [CMake] Re: CMake, CPack, RPM

Thanks for your prompt reply. To some extent you're answering questions that come from me being an RPM newbie. My problem with the Source RPM generation is that it requires that my system -- the one building the source RPM, doesn't have CMake installed as an RPM.When I try and generate the so

[CMake] CPack combine source and binary

Is there some way to combine source and binary into a single package, specifically in the way described below? I have: source in project/sources binaries in project/build Right now, the closest I've gotten is installing the sources, then getting the .zip file to contain zip/build zip/build/source

[CMake] CPack NSIS Silent install option

Would be nice to be able to define a default option for uninstall message box for silent install.. something like CPACK_NSIS_SILENT_UNINSTALL_DEFAULT which could be set with SET( CPACK_NSIS_SILENT_UNINSTALL_DEFAULT /SD IDYES ) # or IDNO or something Modify Modules/NSIS.template.in .. add si

[CMake] Looking for Cmake / CPACK documentation

wasn't that hard, but now I am having two problems: 1. I need a custom page with 2 mutual exclusive options. Depending on the selection I need to copy either file A or file B in "Component 1" while I would need to copy file C or D in "component 2". Is this possible with cmake /

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

> I am working on an IBM Power8 RHEL7.2 system and we installed cmake 3.6 > (default cmake from repo was 2.8.12?) but it seems when making a package > the arch is set incorrectly to x86_64 instead of ppc64le. I don't have access to a ppc with Linux but it seems that 'uname -m' (default that is use

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

2016-06-08 9:45 GMT+02:00 Domen Vrankar : > > I am working on an IBM Power8 RHEL7.2 system and we installed cmake 3.6 > > (default cmake from repo was 2.8.12?) but it seems when making a package > > the arch is set incorrectly to x86_64 instead of ppc64le. > > I don't have access to a ppc with Lin

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

> The strange thing is that CMAKE_HOST_SYSTEM_PROCESSOR (outputed by cmake > --system-information) uses the same "uname -m" > see Modules/CMakeDetermineSystem.cmake. > > So there is something odd to have one right and the other wrong... In that case it's quite possible that CPACK_RPM_PACKAGE_ARCHI

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

Domen Vrankar writes: > > > The strange thing is that CMAKE_HOST_SYSTEM_PROCESSOR (outputed by cmake > > --system-information) uses the same "uname -m" > > see Modules/CMakeDetermineSystem.cmake. > > > > So there is something odd to have one right and the other wrong... > > In that case it's qu

Re: [CMake] cpack ppc64le rhel7.2 CPACK_RPM_PACKAGE_ARCHITECTURE

I was able to verify, btw, that Fedora 19 + Power8 outputs ppc64le for uname -m so I assume it works correctly on EL7 as well. Testead via an IBM machine hosted at the OSU Open Source Lab that we can access and use for testing. - Chuck On Wed, Jun 8, 2016 at 10:33 AM, M Kelly wrote: > Domen Vr

[CMake] CPack source package install location

Hi I have a very standard CPack configuration for deb package. I have two questions: 1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB" This is supposedly a binary package but when I install it on the machine I see header files being installed in /usr/include. Is this no

Re: [CMake] CPack change file extension

Hey, you're working on Windows, right? I think you can do that if you create an additional target and call that target. So let's say, you have this 'hello.cpp', and you generate with CMake a solution. This is an example of a CMakeLists.txt > cmake_minimum_required(VERSION 3.4) > project(cpack_zi

Re: [CMake] CPack change file extension

Hey Kristian, Thx for your answer. Iv've already done this like in your solution. I have a seperated target which depends on my create zip target and use ${CMAKE_COMMAND} -e copy to copy the file to my target directory (so the solution is platform independent), and leaf the original zip in the

Re: [CMake] CPack change file extension

> Do you have any special reason why your rename target depends on PACKAGE, is this the target which cpack is using? I think so ... 2016-08-26 20:01 GMT+02:00 tonka3...@gmail.com : > Hey Kristian, > > Thx for your answer. Iv've already done this like in your solution. I have > a seperated target

Re: [CMake] CPack change file extension

HI all, package is a builtin target unless things have changed you cannot depend on a builtin target. https://gitlab.kitware.com/cmake/cmake/issues/8438 https://cmake.org/Bug/view.php?id=8438 Personnally I would explicitely call CPack in my custom target in order to be sure that the zip is up-to-

[CMake] CPack, Debian packages and libraries

Hi everyone, I'm trying to configure CPack for packaging an executable and some shared libraries the application depends on. Both application and libraries are built by CMake. For NSIS, this works just fine, the installer includes all necessary files. However, the CPack Debian generator seems

[CMake] CPack: Project and independent subproject

Hello everyone, My c++ project contains a Library folder, an Applications folder and a Demos folder like this: Project/ |-> Library/ |-> include/ |-> src/ |-> Applications/ |-> appliA/

Re: [CMake] cpack generators for Windows

2012/11/5 Bogdan Cristea : > Hi > > NSIS seems to be quite outdated and no longer developed, There seems to be relatively recent commit in the repository though: http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/ there is some evolution there as well: http://code.google.com/p/unsis/ > are

Re: [CMake] cpack generators for Windows

On Monday 05 November 2012 13:57:04 you wrote: > There seems to be relatively recent commit in the repository though: > http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/ The latest release is 2.46, December 2009. I have not tried yet the version from trunk, but I have noticed in Win8 some

Re: [CMake] cpack generators for Windows

2012/11/5 Bogdan Cristea : > > On Monday 05 November 2012 13:57:04 you wrote: >> There seems to be relatively recent commit in the repository though: >> http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/ > > The latest release is 2.46, December 2009. I have not tried yet the version > from tru

Re: [CMake] Cpack not packaging anything

Run: VERBOSE=1 make package Then, run the same command line that 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 subdirectories

Re: [CMake] Cpack not packaging anything

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 picks the files from there. Normal behaviour is to install in a temporary loc

Re: [CMake] Cpack not packaging anything

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 > picks the files from there. Normal behavio

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 picks the

Re: [CMake] Cpack not packaging anything

2012/11/26 Thomas Nilsson : > > 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, t

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 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 work that w

[CMake] cpack deb and multiarch support

I build and pack my software (a library) with cmake/cpack and it works great, thanx for this great tool. But I'm not able to build a multiarch-debian package. My install directives are multiarch aware (using GNUInstallDirs) and I build the library on different buildmachines, so no crosscomp

[CMake] CPACK and cmake install(targets

Hi, I try to package a built shared library on windows. In the CMAKE file for where the dll and import lib is created I have install(TARGETS ${target} RUNTIME DESTINATION bin LIBRARY DESTINATION lib ARCHIVE DESTINATION lib COMPONENT rr_core ) When executing the

[CMake] CPack RPM with COMPONENTS packaging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I cannot manage to make COMPONENT packaging with RPM to work. I clearly see that the CPackRPM.cmake module contains stuff to do so, but I cannot manage to make it work at all. Even the ComponentExampleStart that is given on some of CMake

[CMake] CPack Generator-specific install commands

mands, I'll have to include them in a Cpack_Project_config_file, which I have done as well. However, I'm not able to include install() commands in this file for some reason. I'd like to include an additional file in only the tgz package. Is there a way to do this (without reso

[CMake] cpack error in visual studio

Hi, I am trying CPack in visual studio. When I build "PACKAGE" it throws me an error like this: CMake Error at C:/BuildDir1/src/cmake_install.cmake:38 (message): ABSOLUTE path INSTALL DESTINATION forbidden (by caller): C:/BuildDir1/src/Debug/QtGuid4.dll;C:/BuildDir1/src/Debug/QtCored4.dll;

[CMake] CPack: Add PATH to .profile

Hi, Is it possible to create custom components in CPack to add CMAKE_INSTALL_PREFIX/bin to the user ~/.profile? I would like to have an additional entry in the GUI created with PackageMaker that the user could select to patch the .profile. Using install(SCRIPT ...) in CMake the patch my own .pr

Re: [CMake] CPack, Wix using util:XmlFile

o add this option to the existing version of cmake\cpack? Does Cmake provide any utility to modify an xml file? Currently it is not possible to pass custom arguments to the WiX commands executed by CPack. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

Re: [CMake] CPack, Wix using util:XmlFile

ail.com To: laasu...@hotmail.com; cmake@cmake.org Subject: Re: [CMake] CPack, Wix using util:XmlFile On 11/08/2013 09:09 AM, Lars Lars wrote: Using CPack to generate a msi using a custom wix template. I would like to add an ut

Re: [CMake] CPack, Wix using util:XmlFile

On 10.11.2013 17:46, Lars Lars wrote: Just a follow up question, how does CPack invoke candle and light? On Windows 7, using Process Monitor I do see these executables being spawned into a separate process when doing cpack -G "WIX". I am not entirely sure what you mean by "how". But you ca

Re: [CMake] CPack, Wix using util:XmlFile

Date: Sun, 10 Nov 2013 21:20:47 +0100 From: nilsglad...@gmail.com To: laasu...@hotmail.com; cmake@cmake.org Subject: Re: [CMake] CPack, Wix using util:XmlFile On 10.11.2013 17:46, Lars Lars wrote: Just a follow up question

Re: [CMake] CPack, Wix using util:XmlFile

On 11/11/2013 09:21 AM, Lars Lars wrote: I am still quite new to CMake so execuse the igorance but does merging the issue into next mean it will be included in the next release? It means it is being tested on the Dashboards and assuming there are no issues it will be merged to "master" which i

Re: [CMake] CPack WIX: Using FirewallException

On 11/12/2013 03:46 AM, Daiwei Li wrote: Hello, I'm having trouble adding a FirewallException (http://wixtoolset.org/documentation/manual/v3/xsd%5Cfirewall%5Cfirewallexception.html) element for my main executable. The documentation says that it must have a File or Component parent, both of wh

Re: [CMake] CPack WIX: Using FirewallException

Hi Nils, Yes, I was happy to see that you just added the ability to specify WIX Light and Candle extensions to CMake. I built the next branch from source and adding WixFirewallExtension worked just fine. I would be agreeable to a CMake list variable with key-value (target - xml snippet?) pairs to

[CMake] CPack install dirs pr component

How can I specify different install dir prefix for two components using CPack and Wix generator? The current setup installs runtime files to C:\Program Files\MyCompany\bin and data to C:\Program Files\MyCompany\data. We would like to place the data files in for instance c:\data. The setup has

[CMake] CPack RPM with file path "@"

We have some install files under directory xxx/@temp/yyy/ For CMake 2.8.11.1 "cpack -configure " run OK But on Fedora 19+ CMake 2.8.12.x has fix for mantis ticket 0014063 Patch file name: 0001-CPackRPM-protect-character-in-filename-processed-in-.patch

[CMake] CPACK issue with symbolic links

While to trying to create an RPM package using CPACK, we are encountering an issue when symbolic links are present. We are using the CPACK_INSTALLED_DIRECTORIES to specify the directories for packaging. It seems like CPACK is not in the correct directory when creating the symbolic link. /buildd

[CMake] CPack and PackageMaker hide pages

Is it possible to hide some of the pages used in PackageMaker? For example if I don't want to show the license dialog. Best Regards -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to s

Re: [CMake] CPack+ NSIS Template modificaiton

2014-03-20 10:02 GMT+01:00 Lloyd : > Hi, > > We are using NSIS to install our application. It makes use of custom NSIS > plugin and MUI2 based custom interface. In order to accommodate this, I > thought of creating a new NSIS template for our project. > > I have gone through the existing NSIS templ

[CMake] cpack and post install scripts

So it seems that CPack doesn't run the post install scripts? Is it supposed to? Clint ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] Cpack with Bundleutilities on Windows

Hello everyone,   I'm new to cmake so this will be a, more or less, stupid question. I'm creating an multiplatform application that is dependent on curl, Qt, and ffmpeg. I'd like to link them statically.   On Windows is the need to include the *.dll files. I tried to use fixup_bundle() for thi

[CMake] CPack and user .spec file

Hello all, I'm fairly new to CPack and, while I was able to successfully package (RPM) standalone applications that use CMake, I'm having difficulties with packaging an application using a custom .spec file. I have an application repository that is built with CMake, but requires additional/custom

[CMake] [CPack] Avoiding packaging (some) dependencies

Hi everyone, I have particular problem which I'm unable to solve. Lets say there are following components: - Main: library/executable - Ignorable: Main requires it to build, but not for packaging Main simply defines: add_dependencies(Main Ignorable) FindIgnorable.cmake contains something like

Re: [CMake] CPack disable build all

Le ven. 9 nov. 2018 à 17:22, DKLind a écrit : > I have a very large project where each sub-project creates a debian > package. > > When "make/ninja package" is specified, it performs a "make/ninja all" > before packaging. I would prefer to perform a "make/ninja all" myself > before > I doing a "m

[CMake] CPack and WIX: Preselected components

With the NSIS generator I can create a dialog with a drop_down list with two elements default and developer. Default is selected by default when the dialog starts, so the default parts of the package are installed. Selecting developer the devlop parts are installed and the default files not. How

Re: [CMake] CPack general question and example

2010/11/15 David Doria : > I just heard about CPack and started playing with it. Which version of CMake/CPack are you using? > I tried to make an RPM of a simple VTK program: > > http://www.cmake.org/Wiki/CMake/CPackExample > > When I run 'make package', I get an err

Re: [CMake] CPack general question and example

> -Original Message- > From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of > David Doria > Sent: Monday, November 15, 2010 10:37 PM > To: cmake@cmake.org > Subject: [CMake] CPack general question and example > > I just heard about CPack

Re: [CMake] CPack general question and example

> You need  INSTALL commands for everything you want to be in the package > > For your example: > > ADD_EXECUTABLE(DistanceBetweenPoints DistanceBetweenPoints.cxx) > INSTALL(TARGETS DistanceBetweenPoints DESTINATION bin) # Add this for CPack > to work > > Then both "make install" and "make package

Re: [CMake] CPack general question and example

On Mon, Nov 15, 2010 at 05:57:04PM -0500, cmake-requ...@cmake.org wrote: > Message: 2 > Date: Mon, 15 Nov 2010 16:37:05 -0500 > From: David Doria > Subject: [CMake] CPack general question and example > To: cmake@cmake.org > Message-ID: > > Content-Type: text/p

Re: [CMake] CPack general question and example

Hi David, On Tuesday 16 November 2010 03:54:57 David Doria wrote: > > You need INSTALL commands for everything you want to be in the package > > > > For your example: > > > > ADD_EXECUTABLE(DistanceBetweenPoints DistanceBetweenPoints.cxx) > > INSTALL(TARGETS DistanceBetweenPoints DESTINATION bin

Re: [CMake] CPack general question and example

Great, it's working. The only thing that was required was: SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "David Doria") Here is the working example: http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB The page you sent (http://www.vtk.org/Wiki/CMake:CPackPackageGenerators#DEB_.28UNIX

Re: [CMake] CPack general question and example

2010/11/16 David Doria : > Great, it's working.  The only thing that was required was: > > SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "David Doria") > > Here is the working example: > http://www.cmake.org/Wiki/CMake/CPack/Examples/Linux/DEB > > The p

Re: [CMake] cpack, deb file & static libraries

Am Samstag, 20. November 2010 schrieb Paolo Zaffino: > Dear all, > I builded a deb file using cpack. > The package work fine but I have a question for you. > During the compiling (run by cpack command) are generated some static > libraries that will be included into the package. > I don't want incl

Re: [CMake] cpack, deb file & static libraries

2010/11/20 Paolo Zaffino : > Dear all, > I builded a deb file using cpack. > The package work fine but I have a question for you. > During the compiling (run by cpack command) are generated some static > libraries that will be included into the package. > I don't want include the *.a files...do you

Re: [CMake] cpack, deb file & static libraries

2010/11/20 Paolo Zaffino : > I try to explain better: > When I compile my source code, for building the foo executable is needed the > library bar.a > Both the files are building during the compile process...into the deb > package I want include foo but I don't want include bar.a Building and pack

[CMake] CPack, fixup_bundle, macdeployqt, and QTBUG-5952

Me again, with another issue: On Mac, I'm running into the problem described in QTBUG-5952: http://bugreports.qt.nokia.com/browse/QTBUG-5952 where my CPack generated D&D installer yields an installed app fails with a log message like "Qt internal error: qt_menu.nib could not be loaded." This

Re: [CMake] cpack, debian and python virtualenvs:

Probably comes from here: cmCPackDebGenerator.cxx: this->SetOptionIfNotSet("CPACK_PACKAGING_INSTALL_PREFIX", "/usr"); Try setting that variable in your CMakeLists.txt file, too. HTH, David On Thu, Feb 10, 2011 at 4:44 PM, Nathan J. Mehl wrote: > What I'm trying to do: use cpack to turn a dire

Re: [CMake] cpack, debian and python virtualenvs:

On Thu, Feb 10, 2011 at 1:56 PM, David Cole wrote: > Probably comes from here: > cmCPackDebGenerator.cxx: > this->SetOptionIfNotSet("CPACK_PACKAGING_INSTALL_PREFIX", "/usr"); > *DING* Sigh, would have been nice if that had been anywhere in the documentation, or called out in any of the module/t

Re: [CMake] cpack, debian and python virtualenvs:

2011/2/10 Nathan J. Mehl : > > > On Thu, Feb 10, 2011 at 1:56 PM, David Cole wrote: >> >> Probably comes from here: >> cmCPackDebGenerator.cxx: >> this->SetOptionIfNotSet("CPACK_PACKAGING_INSTALL_PREFIX", "/usr"); > > *DING* > > Sigh, would have been nice if that had been anywhere in the documenta

Re: [CMake] cpack, debian and python virtualenvs:

On Thu, Feb 10, 2011 at 3:26 PM, Eric Noulard wrote: > 2011/2/10 Nathan J. Mehl : > > > > Sigh, would have been nice if that had been anywhere in the > documentation, > > or called out in any of the module/template files. But any landing you > walk > > away from... > > All CPack generators use th

Re: [CMake] CPack -- adding license to files

Sounds like more of a job for perl, python or ruby to me. On Fri, Jul 1, 2011 at 12:17 PM, Raymond Wan wrote: > Hi all, > > I was wondering if there is an easy/automated way that I can get CMake > or CPack to add a license to every source file prior to distribution > of the source. Of course,

[CMake] CPack: Use an external tar program

Hi, AIUI, cpack's tar support is done natively using libarchive. I'd like to instead use an external tar binary, in this case one which uses pigz as the gzip backend, as it is massively faster on the hardware I am building on. Is there some trick I've not found to allow this, or is it unsupporte

Re: [CMake] CPack: Bundle Generator and fixup_bundle

On Monday, July 11, 2011 01:01:24 pm Dominik Schmidt wrote: > Hello List! > > I'm trying to use the Bundle Generator for Mac OS X and am facing the > following problem: > > bundle_fixup() from BundleUtilities would need to be called after > generating the app *before* generating the .dmg, but loo

Re: [CMake] CPack: Bundle Generator and fixup_bundle

Hi Dominik, If I understood properly your problem ... You could have a look at line 40 of https://github.com/Slicer/Slicer/blob/master/SlicerCPack.cmake # HACK - For a given directory, "install(SCRIPT ...)" rule will be evaluated first, # let's make sure the following install rule is evaluat

Re: [CMake] CPack: Bundle Generator and fixup_bundle

Hey! First of all: Thanks for your quick replies to both of you! Am 11.07.2011 21:09, schrieb Clinton Stimpson: > Have you considered using the DragNDrop generator instead? Yep, but I want to use the Bundle Generator and I think it should be possible to do so. Of course, there's not much to bu

Re: [CMake] CPack: Bundle Generator and fixup_bundle

By the way, I'm on #cmake@freenode as domme if anyone likes to discuss with me there I'm present most of the day (at least until tomorrow evening and again after Sunday) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http

Re: [CMake] [CPACK] CPack not working properly

2011/8/23 Renato Utsch : > Hello CMake Experts! > > I don't know if it's here that I have to ask, so if I'm wrong, please tell > me. > > I used the CPack and it stopped making the binary package at the middle of > the process, running like this: >From the trace you gave it does not stopped it goes

[CMake] CPack RPM: why not ---.rpm filename?

When I build a RPM with current CVS CMAKE/CPack for project the file name of the generated rpm is: --Linux.rpm The common filename for an rpm is ---.rpm Putting "Linux" in the file name doesn't provide much information because I don't know any other OS that uses th

<    2   3   4   5   6   7   8   9   10   11   >