Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Elvis Stansvik
Den tis 23 okt. 2018 kl 18:46 skrev Elvis Stansvik : > > Den tis 23 okt. 2018 kl 18:26 skrev Elvis Stansvik > : > > > > Just going to jump in here and show how we did it (on the bus with just my > > phone so will be a bit terse): > > > > packaging/InstallWindowsDeps.cmake: > > > >

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Elvis Stansvik
Den tis 23 okt. 2018 kl 18:26 skrev Elvis Stansvik : > > Just going to jump in here and show how we did it (on the bus with just my > phone so will be a bit terse): > > packaging/InstallWindowsDeps.cmake: > > include(BundleUtilities) > > # Dependant executables/libraries > set(INSIGHT_ARTIFACTS >

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Elvis Stansvik
Just going to jump in here and show how we did it (on the bus with just my phone so will be a bit terse): packaging/InstallWindowsDeps.cmake: include(BundleUtilities) # Dependant executables/libraries set(INSIGHT_ARTIFACTS "${CMAKE_INSTALL_PREFIX}/orexplore-insight.exe"

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Anatoly Belyaev
I tried example like this set(test_SRC main.cpp) install(CODE "MESSAGE(\"CODE1\")") add_executable(test ${test_SRC}) install(TARGETS test DESTINATION ${CMAKE_INSTALL_BINDIR}) install(CODE "MESSAGE(\"CODE2\")") Then i checked cmake_install.cmake and "CODE1" cmd will be executed before strip

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Eric Noulard
Le mar. 23 oct. 2018 à 12:06, Craig Scott a écrit : > > > On Tue, Oct 23, 2018 at 4:43 PM Eric Noulard > wrote: > >> Le lun. 22 oct. 2018 à 23:05, Craig Scott a >> écrit : >> >>> Yes I agree that having build rpath is useful. I am not aware of any mechanism that enable calling some

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-23 Thread Craig Scott
On Tue, Oct 23, 2018 at 4:43 PM Eric Noulard wrote: > Le lun. 22 oct. 2018 à 23:05, Craig Scott a > écrit : > >> >>> Yes I agree that having build rpath is useful. >>> I am not aware of any mechanism that enable calling some tool during >>> CPack's install step. >>> Moreover I don't use MacOS

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-22 Thread Eric Noulard
Le lun. 22 oct. 2018 à 23:05, Craig Scott a écrit : > >> Yes I agree that having build rpath is useful. >> I am not aware of any mechanism that enable calling some tool during >> CPack's install step. >> Moreover I don't use MacOS at all so I don't have any experience with >> PackageMaker. >> >>

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-22 Thread Craig Scott
On Tue, Oct 23, 2018 at 12:32 AM Eric Noulard wrote: > > > Le lun. 22 oct. 2018 à 11:56, Anatoly Belyaev a > écrit : > >> We use "PackageMaker" generator on MacOS. But i don't think it is CPack >> specific tool does call strip command. The code for RPATH rewrite and >> strip cmd is located in

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-22 Thread Eric Noulard
Le lun. 22 oct. 2018 à 11:56, Anatoly Belyaev a écrit : > We use "PackageMaker" generator on MacOS. But i don't think it is CPack > specific tool does call strip command. The code for RPATH rewrite and > strip cmd is located in cmake_install.cmake. As i understand CPack calls > make install to

Re: [CMake] Signing individual binary and problem with PackageMaker CPack generator

2018-10-22 Thread Anatoly Belyaev
We use "PackageMaker" generator on MacOS.  But i don't think it is CPack specific tool does call strip command.  The code for RPATH rewrite and strip cmd is located in cmake_install.cmake. As i understand CPack calls make install to tmp dir and then creates package. Having different RPATH for