[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

[CMake] CPack`ing a bunch of command line tools on OS/X

Hello, I try to pack a bunch of command line tools (and some additional data files) into an OS/X installer. When the installer is running, it should install / copy the command line tools and adjust the PATH variable (or what ever mean that comes close, to make the tools available). I use a

Re: [CMake] CMake | CMake/CPack do not print out messages as they progress (#19343)

I found out the problem was an old ninja version. I am closing the bug report. El 06/06/19 a las 12:27, Brad King escribió: GitLab I tried CMake 3.14.5 and 3.15.0-rc1 on your example. They both behave the same. Running |ninja bundle| shows incremental output from cpack. Alternatively

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 22:16, Gonzalo Garramuño escribió: El 30/5/19 a las 21:36, Zan Lynx escribió: RPM files are not cpio. They contain a cpio. Use rpm2cpio as a filter. Thanks for that.  Using: rpm2cpio mrViewer-v5.0.7-Linux-64.rpm | cpio -idmv I can extract all the contents of the archive

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 21:36, Zan Lynx escribió: RPM files are not cpio. They contain a cpio. Use rpm2cpio as a filter. Thanks for that.  Using: rpm2cpio mrViewer-v5.0.7-Linux-64.rpm | cpio -idmv I can extract all the contents of the archive with no errors. However, rpm -i bails out with a cpio:

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

On May 30, 2019 5:21:59 PM MST, "Gonzalo Garramuño" wrote: > >El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: >> rpm -ql mrViewer-v5.0.6-Linux-64.rpm > >If I run cpio -i < mrViewer-v5.0.6-Linux-64.rpm > >I get a bunch of warnings of Incorrect numbers (and garbage) and Cannot > >make mknod:

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

El 30/5/19 a las 12:51, Gonzalo Garramuño escribió: rpm -ql mrViewer-v5.0.6-Linux-64.rpm If I run cpio -i < mrViewer-v5.0.6-Linux-64.rpm I get a bunch of warnings of Incorrect numbers (and garbage) and Cannot make mknod: the multibyte or extended character is incomplete or invalid, and

Re: [CMake] Cmake/Cpack creates a corrupt .rpm

ailed You can find the RPM file here: https://sourceforge.net/projects/mrviewer/files/v5.0.6/mrViewer-v5.0.6-Linux-64.rpm/download If I use: rpm -ql mrViewer-v5.0.6-Linux-64.rpm all files are there.  However, when installing, the installer fails on reaching the lib directory of the rpm. C

[CMake] Cmake/Cpack creates a corrupt .rpm

ge.net/projects/mrviewer/files/v5.0.6/mrViewer-v5.0.6-Linux-64.rpm/download If I use: rpm -ql mrViewer-v5.0.6-Linux-64.rpm all files are there.  However, when installing, the installer fails on reaching the lib directory of the rpm. CMake/CPack used to build the rpm just fine some (long) ve

Re: [CMake] CPack/WiX shortcuts with custom arguments

To follow up on this, I tried creating a .bat file to run my program with the required command line arguments, but I was unable to add a shortcut to the .bat file because cmake appends ".exe" to the name of the executable in CPACK_PACKAGE_EXECUTABLES. I think the only way to make it work is to

[CMake] CPack/WiX shortcuts with custom arguments

Hi, I'm attempting to transition from NSIS to WiX for our Windows installer and have been unable to find a way to create customised shortcuts with WiX (I would like to specify both the working directory and command line parameters). Some approaches I've tried are: * Specifying

Re: [CMake] CPack and WIX: Preselected components

Micha, Unfortunately, the WiX generator does not currently support component installation, which is what's needed to make the INSTALL_TYPES argument work. We would welcome a merge request which adds this support. Kyle On Thu, 2019-01-17 at 19:28 +0100, Micha Renner wrote: > With the NSIS

[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 RPM: file XXX conflicts with file from package filesystem-yyy...

Le mar. 27 nov. 2018 à 14:56, Mario Emmenlauer a écrit : > > Dear Eric, > > just to let you know, your suggestion of using a post-install-script > for all system-wide links and files was indeed the solution to a working > RPM package. Now my files are completely encapsulated in /opt/PKGNAME/ >

Re: [CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

Dear Eric, just to let you know, your suggestion of using a post-install-script for all system-wide links and files was indeed the solution to a working RPM package. Now my files are completely encapsulated in /opt/PKGNAME/ and install works fine. Cheers and Thanks, Mario On 23.11.18

Re: [CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

Dear Eric, thanks a lot for this help! I think I have the pointers to move forward! One more detail below: On 23.11.18 11:36, Eric Noulard wrote: > Le ven. 23 nov. 2018 à 11:10, Mario Emmenlauer > a écrit : > Dear Eric, thanks for the help! Below more: > >

Re: [CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

Le ven. 23 nov. 2018 à 11:10, Mario Emmenlauer a écrit : > > Dear Eric, thanks for the help! Below more: > > On 22.11.18 18:20, Eric Noulard wrote: > > Le jeu. 22 nov. 2018 à 16:16, Mario Emmenlauer > a écri > > I'm trying to build an RPM with CPack, and

Re: [CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

Dear Eric, thanks for the help! Below more: On 22.11.18 18:20, Eric Noulard wrote: > Le jeu. 22 nov. 2018 à 16:16, Mario Emmenlauer > a écri > I'm trying to build an RPM with CPack, and everything seems to work, > but the resulting package can not be

Re: [CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

Le jeu. 22 nov. 2018 à 16:16, Mario Emmenlauer a écri > > I'm trying to build an RPM with CPack, and everything seems to work, > but the resulting package can not be installed. I get Transaction check > error: > file / from install of conflicts with file from package >

[CMake] CPack RPM: file XXX conflicts with file from package filesystem-yyy...

I'm trying to build an RPM with CPack, and everything seems to work, but the resulting package can not be installed. I get Transaction check error: file / from install of conflicts with file from package filesystem-3.2-25.el7.x86_64 file /opt from install of conflicts with file from

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

[CMake] CPack disable build all

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 "make/ninja package". I want to create a package for just one

Re: [CMake] CPack multiple packages

2018-07-19 18:00 GMT+02:00 dbegun via CMake : > I have a project where a lib and a binary requiring the lib are built in > separate subdirs of the project root. Each dir contains its own > CMakeLists.txt with build/install targets, and there is also a top level > one, which mainly just adds

[CMake] CPack multiple packages

I have a project where a lib and a binary requiring the lib are built in separate subdirs of the project root. Each dir contains its own CMakeLists.txt with build/install targets, and there is also a top level one, which mainly just adds subdirectories etc. I want to add .deb package generation

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

Thank you for your answer! I was afraid there was no other option. Problem is that "Ignorable" is a transient dependency of a target which I need (both don't specify components) and therefore both are somewhat out of my control, but I guess modification to them will be necessary. I wasn't aware

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

2018-05-16 9:33 GMT+02:00 Drago Trusk : > 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

[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

[CMake] CPack + WIX + vcredist, is it possible?

Hello, Is it possible to use CPack with WIX (Windows Installer) generator and run vcredist_*.exe at install time? Some considerations: * WIX cannot run two installers at once so something called Burn has to be used. I'm not sure whether CPack can do it, I cannot find any relevant documentation.

Re: [CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

2018-01-04 22:42 GMT+01:00 Sam Lunt : > Hi Domen, > > Thanks for the reply, but that doesn't seem to work for me. I modified > my example to add this function call: > > list(APPEND CPACK_RPM_RELOCATION_PATHS > ${CPACK_PACKAGING_INSTALL_PREFIX} > ) > The

Re: [CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

Hi Domen, Thanks for the reply, but that doesn't seem to work for me. I modified my example to add this function call: list(APPEND CPACK_RPM_RELOCATION_PATHS ${CPACK_PACKAGING_INSTALL_PREFIX} ) that silences the warnings, but it still prepends the CPACK_PACKAGING_INSTALL_PREFIX when

Re: [CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

2018-01-03 22:40 GMT+01:00 Sam Lunt : > I am trying to set a per-component value for > CPACK_PACKAGING_INSTALL_PREFIX when using the RPM generator, but I > haven't been able to do so. > > I would like to be able to: > 1. Install using "make install" (or cmake

[CMake] CPack per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using RPM generator

I am trying to set a per-component value for CPACK_PACKAGING_INSTALL_PREFIX when using the RPM generator, but I haven't been able to do so. I would like to be able to: 1. Install using "make install" (or cmake --build ${BUILD_DIR} --target install) and have CMAKE_INSTALL_PREFIX control the

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 20:35 GMT+01:00 DKLind : > Domen Vrankar wrote > > I'm a bit confused. Is there something missing in the patch? > > Attached patch only adds per component version override - it doesn't even > > touch the multiple calls to `include(CPack)` and naming of different >

Re: [CMake] CPack: Create debian packge for each sub-project

Domen Vrankar wrote > I'm a bit confused. Is there something missing in the patch? > Attached patch only adds per component version override - it doesn't even > touch the multiple calls to `include(CPack)` and naming of different > packages (not their components but different package names). > >

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-04 19:57 GMT+01:00 DKLind : > Domen Vrankar wrote > > product_1-component_1-1.0.0 > > product_1-component_2-1.0.0 > > product_2-component_1-3.5.7 > > product_2-component_2-3.5.7 > > This too is what my patch fixes. Attached is the patch. > > CPackDeb.patch >

Re: [CMake] CPack: Create debian packge for each sub-project

Domen Vrankar wrote > product_1-component_1-1.0.0 > product_1-component_2-1.0.0 > product_2-component_1-3.5.7 > product_2-component_2-3.5.7 This too is what my patch fixes. Attached is the patch. CPackDeb.patch -- Sent from:

Re: [CMake] CPack: Create debian packge for each sub-project

e independently. The first option is supported by the intuitive use of Linux distributions by simply running something like "sudo apt search libboost" but it's possible that the alternative way of packaging is possibly also feasible for others (and what we did is simply an ug

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-01 16:47 GMT+01:00 DKLind : > This is precisely my situation. I have a large project where 50+ packages > are > generated. I wanted, needed, to be able to set each packages' version > uniquely. Using the CPACK_DEBAIN__PACKAGE_VERSION variable > seemed > to be the

Re: [CMake] CPack: Create debian packge for each sub-project

2017-12-01 5:41 GMT+01:00 Craig Scott : > > > On Fri, Dec 1, 2017 at 11:15 AM, Domen Vrankar > wrote: > >> 2017-11-29 17:07 GMT+01:00 DKLind : >> >>> I have finally found time to work on a patch so >>>

Re: [CMake] CPack: Create debian packge for each sub-project

This is precisely my situation. I have a large project where 50+ packages are generated. I wanted, needed, to be able to set each packages' version uniquely. Using the CPACK_DEBAIN__PACKAGE_VERSION variable seemed to be the correct way, except it doesn't work. My patch allows

Re: [CMake] CPack: Create debian packge for each sub-project

On Fri, Dec 1, 2017 at 11:15 AM, Domen Vrankar wrote: > 2017-11-29 17:07 GMT+01:00 DKLind : > >> I have finally found time to work on a patch so >> CPACK_DEBAIN__PACKAGE_VERSION is recognized. I am amazed how >> simple the fix actually is. >> >> I

Re: [CMake] CPack: Create debian packge for each sub-project

2017-11-29 17:07 GMT+01:00 DKLind : > I have finally found time to work on a patch so > CPACK_DEBAIN__PACKAGE_VERSION is recognized. I am amazed how > simple the fix actually is. > > I plan on submitting a formal patch soon for Debian and RPM. I don't know > anything about

Re: [CMake] CPack: Create debian packge for each sub-project

I have finally found time to work on a patch so CPACK_DEBAIN__PACKAGE_VERSION is recognized. I am amazed how simple the fix actually is. I plan on submitting a formal patch soon for Debian and RPM. I don't know anything about other CMake packaging features that might benefit from this patch.

Re: [CMake] CPack OS X bundle : generator expression for CPACK_BUNDLE_STARTUP_COMMAND

Hi, `set()` is evaluated at configuration time and as of CMake 3.10 does not accept genexps. You can refer to this diagram for better understanding of the general CMake pipeline: Therefore, > SET ( APP_LOCATION "$" ) >

[CMake] CPack OS X bundle : generator expression for CPACK_BUNDLE_STARTUP_COMMAND

I am using CMake 3.10 I can't seems to find a way to tell the OS X bundle where to find the compiled binary. I get the following errors: Run CPack packaging tool... CPack: Create package using Bundle CPack: Install projects CPack: - Run preinstall target for: OSXBundle CPack: - Install project:

Re: [CMake] [CPack] hdiutil error while executing cpack on macOS

; package. I tried to search for this message in the ML archives and elsewhere > but wasn't able to find any conclusive solution, so I'm hoping someone with > more experience with CPack may be able to help. My environment is: > > macOS 10.13 > cmake/cpack 3.9.1 > > The output I'm gett

[CMake] [CPack] hdiutil error while executing cpack on macOS

is: macOS 10.13 cmake/cpack 3.9.1 The output I'm getting is: CPack: Create package using DragNDrop CPack: Install projects CPack: - Install project: SuperCollider CPack: - Install component: Runtime CPack: - Install component: Unspecified CPack: Create package CPack Error: Error executing: /usr

Re: [CMake] CPack Multicore Usage

> > cause cpack does not "rebuild" the software again, it uses the compiled > software and just starts the "install" into its _CPack_Packages > subdirectories > Just running `cpack` does not. However, CMake does generate a "package" make target that is tied into your dependencies, so if instead

Re: [CMake] CPack: Create debian packge for each sub-project

Here's a little trick I learned. Executing the custom target, "make package_target target=xyz", will build the target and call cpack to create the package. Additional parameters can be passed by putting the target value in quotes (make package_target target="xyz -j4"). Executing cpack causes the

Re: [CMake] CPack Multicore Usage

ware again, it uses the compiled software and just starts the "install" into its _CPack_Packages subdirectories Thank for your patience :-) -Ursprüngliche Nachricht- Von:Chuck Atkins <chuck.atk...@kitware.com> Gesendet: Fr 21.07.2017 21:32 Betreff:Re: [CM

Re: [CMake] CPack: Create debian packge for each sub-project

On Mon, Jul 24, 2017 at 6:13 AM, Gonzalo Garramuño wrote: > > > El 23/07/17 a las 12:37, DKLind escribió: > >> I forgot, I also have a question about "make package". How do I build and >> package just an individual sub-project. As expected, "make " >> works to build, but

Re: [CMake] CPack: Create debian packge for each sub-project

El 23/07/17 a las 12:37, DKLind escribió: I forgot, I also have a question about "make package". How do I build and package just an individual sub-project. As expected, "make " works to build, but there isn't a default target to package an individual sub-project. AFAIK, it is not possible. I

Re: [CMake] CPack: Create debian packge for each sub-project

2017-07-23 17:19 GMT+02:00 DKLind : > Also, curious why CPACK_*COMPONENT*__DESCRIPTION is different > from the other CPACK_*DEBIAN*__PACKAGE_XXX? > Most variables are debian package specific/allow to override general CPack variables specifically for debian packages. For

Re: [CMake] CPack: Create debian packge for each sub-project

I forgot, I also have a question about "make package". How do I build and package just an individual sub-project. As expected, "make " works to build, but there isn't a default target to package an individual sub-project. -- View this message in context:

Re: [CMake] CPack: Create debian packge for each sub-project

Domen, Thanks for the reply to my question. I was aware of the Debian packaging generator page and I also was already setting the component value to uppercase. As documented, I had to use PARENT_SCOPE when setting CPACK_DEBIAN__PACKAGE_XXX values from sub-projects' CMakeLists.txt. Also, curious

Re: [CMake] CPack: Create debian packge for each sub-project

2017-07-22 1:55 GMT+02:00 DKLind : > I have a large project and I need to create a Debian package for each > sub-project (essentially each add_subdirectory). > > I have been experimenting with CPack components as outlined here: >

[CMake] CPack: Create debian packge for each sub-project

I have a large project and I need to create a Debian package for each sub-project (essentially each add_subdirectory). I have been experimenting with CPack components as outlined here:

Re: [CMake] CPack Multicore Usage

> > In calls to cpack only one core is used if Makefiles are used. Is there > any option to enable multicore? > It depends on what your trying to achieve. Typically the bottleneck for CPack is in the compression step of the resulting tar (or rpm, etc.). In that case, CMake is limited by the

Re: [CMake] CPack Multicore Usage

20.07.2017, 11:22, "Jörg Kreuzberger" : > Hi > > My Project is compiling multicore without any problems using Unix makefiles > or ninja. > > In calls to cpack only one core is used if Makefiles are used. Is there any > option to enable multicore? Yes, you should run

[CMake] CPack Multicore Usage

Hi My Project is compiling multicore without any problems using Unix makefiles or ninja. In calls to cpack only one core is used if Makefiles are used. Is there any option to enable multicore? If i use ninja in cpack builds, the cpack build is broken, cause there seems no dependencies

Re: [CMake] CPack install 3rd party shared libraries

age/cmake_install.cmake:37 (include) > > > > CPack Verbose: fixup_bundle: done > > CPack Error: Error when generating package: MyPackage > > > > > > Regards > > Roman > > > > -Ursprüngliche Nachricht- > Von: Elvis Stansvik [mailto:

Re: [CMake] CPack install 3rd party shared libraries

man Wüger <roman.wue...@gmx.at>; CMake MailingList <cmake@cmake.org> Betreff: Re: [CMake] CPack install 3rd party shared libraries (Adding the mailing list back to the list of recepients - It's always good to keep the discussion on the list) 2017-07-19 19:30 GMT+02:00 Roman Wüger

Re: [CMake] CPack install 3rd party shared libraries

explanation? Elvis > > Regards > Roman > > -Ursprüngliche Nachricht- > Von: CMake [mailto:cmake-boun...@cmake.org] Im Auftrag von Roman Wüger > Gesendet: Mittwoch, 19. Juli 2017 19:14 > An: 'Elvis Stansvik' <elvis.stans...@orexplore.com> > Cc: 'CMake Mail

Re: [CMake] CPack install 3rd party shared libraries

gList <cmake@cmake.org> Betreff: Re: [CMake] CPack install 3rd party shared libraries 2017-07-19 16:42 GMT+02:00 David Cole <dlrd...@aol.com>: > Very nice example. Does CMake have a place to put examples like VTK > does...? If so, where is it? And if not, it would be super useful to &

Re: [CMake] CPack install 3rd party shared libraries

2017-07-19 16:42 GMT+02:00 David Cole : > Very nice example. Does CMake have a place to put examples like VTK > does...? If so, where is it? And if not, it would be super useful to > start one somewhere "official." I guess the wiki is for that? Though I think my example should be

Re: [cmake-developers] [CMake] CPack install 3rd party shared libraries

Very nice example. Does CMake have a place to put examples like VTK does...? If so, where is it? And if not, it would be super useful to start one somewhere "official." However, one word of caution on the example. I know it was targeted at Linux, and perhaps for a very simple case it's proper,

Re: [CMake] CPack install 3rd party shared libraries

Very nice example. Does CMake have a place to put examples like VTK does...? If so, where is it? And if not, it would be super useful to start one somewhere "official." However, one word of caution on the example. I know it was targeted at Linux, and perhaps for a very simple case it's proper,

Re: [CMake] CPack install 3rd party shared libraries

2017-07-19 15:57 GMT+02:00 Elvis Stansvik : > 2017-07-19 13:42 GMT+02:00 Roman Wüger : >> The problem with BundleUtilities which Inder is that it doesn't support >> generator expressions. >> >> Maybe I do something wrong? >> But I need to specify

Re: [CMake] CPack install 3rd party shared libraries

2017-07-19 13:42 GMT+02:00 Roman Wüger : > The problem with BundleUtilities which Inder is that it doesn't support > generator expressions. > > Maybe I do something wrong? > But I need to specify the path to the executable (generator expression) and > the paths where to look

Re: [cmake-developers] [CMake] CPack install 3rd party shared libraries

The problem with BundleUtilities which Inder is that it doesn't support generator expressions. Maybe I do something wrong? But I need to specify the path to the executable (generator expression) and the paths where to look for dependencies. Right? Please, could you give me a hint? Regards

Re: [CMake] CPack install 3rd party shared libraries

The problem with BundleUtilities which Inder is that it doesn't support generator expressions. Maybe I do something wrong? But I need to specify the path to the executable (generator expression) and the paths where to look for dependencies. Right? Please, could you give me a hint? Regards

Re: [CMake] CPack install 3rd party shared libraries

2017-07-19 10:24 GMT+02:00 Roman Wüger : > Hello, > > I have a project which depends on a self compiled 3rd party project (boost) > Boost is here only an example, there are other 3rd party libraries too. > > If I call the "install" command on the target, then it would be

[CMake] CPack install 3rd party shared libraries

Hello, I have a project which depends on a self compiled 3rd party project (boost) Boost is here only an example, there are other 3rd party libraries too. If I call the "install" command on the target, then it would be packaged. But how could I add the shared libraries and especially the links

Re: [CMake] CPack and user .spec file

2017-06-20 8:43 GMT-04:00 Domen Vrankar : > Can this not be done from CMakeLists.txt by setting some additional CPACK_* > variables depending on the build environment? The custom bits could be done with CPACK_*, I think, but I haven't spent too much time investigating

Re: [CMake] CPack and user .spec file

> > I have an application repository that is built with CMake, but > requires additional/custom handling when packaging -- hence the need > for a custom .spec file. Can this not be done from CMakeLists.txt by setting some additional CPACK_* variables depending on the build environment? > After

[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

Re: [CMake] CPack - Transaction error

Thank you, that helped! 2017-05-09 15:24 GMT+02:00 Domen Vrankar : >> Transaction check error: >> file /opt from install of ssp-suite-7.1-1.x86_64 conflicts with file >> from package filesystem-3.2-21.el7.x86_64 >> >> Error Summary > > > Directory /opt is already owned

Re: [CMake] CPack - Transaction error

> > Transaction check error: > file /opt from install of ssp-suite-7.1-1.x86_64 conflicts with file > from package filesystem-3.2-21.el7.x86_64 > > Error Summary > Directory /opt is already owned by filesystem package but is not listed in CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST variable. Add /opt

[CMake] CPack - Transaction error

Hi, I want to generate a RPM package. My CMakeLists.txt looks loke this: ## cmake_minimum_required(VERSION 3.5) set(INSTALL_DIR ${CMAKE_INSTALL_PREFIX}/ssp/) install(DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/ssp-suite/" DESTINATION ${INSTALL_DIR}) install(PROGRAMS

Re: [CMake] CPack not detecting pkgbuild or product build

OK, good to know. Best, Ayla > On May 4, 2017, at 6:09 AM, Robert Maynard wrote: > > Hi, > > By default the NSIS generator is enabled. > > On Wed, May 3, 2017 at 6:39 PM, Ayla Khan > wrote: > That worked - thank

Re: [CMake] CPack not detecting pkgbuild or product build

Hi, By default the NSIS generator is enabled. On Wed, May 3, 2017 at 6:39 PM, Ayla Khan wrote: > That worked - thank you! Do I need to add NSIS manually for Windows > installers as well? It looks like CMake finds NSIS without any difficulty > but I’d rather be sure. > >

Re: [CMake] CPack not detecting pkgbuild or product build

That worked - thank you! Do I need to add NSIS manually for Windows installers as well? It looks like CMake finds NSIS without any difficulty but I’d rather be sure. Thanks, Ayla > On May 3, 2017, at 2:56 PM, Robert Maynard wrote: > > You will need to append the

Re: [CMake] CPack not detecting pkgbuild or product build

You will need to append the productbuild type to you CPACK_GENERATOR so it would look like SET(CPACK_GENERATOR "productbuild;STGZ;TGZ") On Wed, May 3, 2017 at 4:14 PM, Ayla Khan wrote: > Thank you Robert. The CPACK_GENERATOR variable is currently set to > “STGZ;TGZ”. When I

Re: [CMake] CPack not detecting pkgbuild or product build

Thank you Robert. The CPACK_GENERATOR variable is currently set to “STGZ;TGZ”. When I installed Xcode, I made sure using xcode-select that the usual command line tools were installed. I can find productbuild in my PATH, but CPACK_BINARY_PRODUCTBUILD is off in CPackConfig.cmake. Do I need to

Re: [CMake] CPack not detecting pkgbuild or product build

Hi Ayla, The packages that are built when executing "make package" is determined by the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally located in the root of your build directory as it is configured ). On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan wrote: >

[CMake] CPack not detecting pkgbuild or product build

I’m trying to build a Mac OS X installer package on 10.10.5 using Xcode 7.2 tools with the CPack that ships with CMake 3.7.2. I can generate a package from the CMake build directory if I call cpack directly on the command line with -G productbuild, but not through the CMake build using make

Re: [CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

2017-03-08 16:23 GMT+01:00 Bernhard Seckinger : > Hi Domen, > > > This came up in the past and if I recall correctly the only workaround > was > > the install(DIRECTORY ... DIRECTORY_PERMISSIONS) that you mentioned. > Please > > file a bug report for this one. > > Where

Re: [CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

Hi Domen, > This came up in the past and if I recall correctly the only workaround was > the install(DIRECTORY ... DIRECTORY_PERMISSIONS) that you mentioned. Please > file a bug report for this one. Where is the best place to do so? Berni -- -- Meine Rätselwebseite: www.croco-puzzle.com --

Re: [CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

2017-03-08 10:00 GMT+01:00 Bernhard Seckinger : > Hi all, > > I'm using cpack to generate a debian package. There are two things that > look > like bugs in cpack to me (although it might also be, that I got something > wrong): > > a) Files, that I install with

[CMake] CPACK, generating deb packages: md5sums and wrong directory permissons

Hi all, I'm using cpack to generate a debian package. There are two things that look like bugs in cpack to me (although it might also be, that I got something wrong): a) Files, that I install with install(FILES ...) get the wrong name in the md5sum section. Names should be e.g. "usr/bin/croco",

[CMake] CPack WIX - disable feature by default

Hello, I’ve create an installer with cpack and WIX (cpack –G WIX). Everything works fine, but I have one big problem. I have 2 features, which are created by cpack(wix). My Problem: I want to deactivate the CM_C_dev feature by default (CPACK_WIX seems

[CMake] cpack logging question

Hi, I am using the cpack variable CPACK_INSTALL_COMMANDS to run an extra command. (First time I do this) I have noticed that whenever the script command fails I get a log with the output in (InstallOtput.log) However when it runs correctly I have no log at all. I have tried to redirect the

Re: [CMake] cpack multiple packages

, Dvir From: Domen Vrankar [mailto:domen.vran...@gmail.com] Sent: Thursday, December 22, 2016 20:43 To: Dvir Yitzchaki <dvir.yitzch...@ceva-dsp.com> Cc: Eric Noulard <eric.noul...@gmail.com>; cmake@cmake.org Subject: Re: [CMake] cpack multiple packages 2016-12-21 12:29 GMT+01:00 Dv

Re: [CMake] cpack multiple packages

2016-12-21 12:29 GMT+01:00 Dvir Yitzchaki : > Thanks, but as I understand a component can only belong to one group. > > How can I get the same component/target on multiple packages? > Usually you wouldn't want to package same file on same location with same filename

Re: [CMake] cpack multiple packages

ke.org Subject: Re: [CMake] cpack multiple packages When playing with component you have 3 major way to package which are governed by the value of CPACK_COMPONENTS_GROUPING: 1 package per component -> set(CPACK_COMPONENTS_GROUPING IGNORE) 1 package for all -> set(CPACK_COMPONE

Re: [CMake] cpack multiple packages

When playing with component you have 3 major way to package which are governed by the value of CPACK_COMPONENTS_GROUPING: 1 package per component -> set(CPACK_COMPONENTS_GROUPING IGNORE) 1 package for all -> set(CPACK_COMPONENTS_GROUPING ALL_COMPONENTS_IN_ONE) 1 package per component group the

[CMake] cpack multiple packages

Hi. I have a big project which produces several zip packages. Some files are common to all packages while others are unique per package. Is there a way to create these packages using cpack? I tried to use components but it seems that either it puts all components in one package or makes one

Re: [CMake] CPACK WIX shortcuts

Yup that did it! Thanks! On Thu, Nov 3, 2016 at 12:10 PM, Nils Gladitz wrote: > On 03.11.2016 19:32, Tiago Macarios wrote: > >> >> >> And I am building it like so: >> mkdir build >> cd build >> cmake .. >> cmake --build . --config Release >> cpack -G WIX >> > > You are

Re: [CMake] CPACK WIX shortcuts

On 03.11.2016 19:32, Tiago Macarios wrote: And I am building it like so: mkdir build cd build cmake .. cmake --build . --config Release cpack -G WIX You are using a multi-configuration generator (Visual Studio). As you do in the build try specifying a configuration to be packaged when

Re: [CMake] CPACK WIX shortcuts

Hi Nils, Here are all the versions of things involved: Windows10 1607 14393.351 cmake 3.6.3 wix 3.10.3 VS 2015 Update 3 14.0.25431.01 I modified the test to be self contained: == cmake_minimum_required(VERSION 3.6) add_executable(h-w hw.cpp)

  1   2   3   4   5   6   7   8   9   10   >