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:
> >
> > include(BundleUt
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
>
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"
"${CMAKE_INSTALL_
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 comm
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 to
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 at
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.
>>
>>
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
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
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
We use CMake
|add_custom_command(TARGET POST_BUILD COMMAND codesign ...) |
for signing executable files on build. It works fine, but when CPack
generates package it rewrites rpath on executable files and call strip
command on them. This changes the file and invalidates the signature. Is
there
11 matches
Mail list logo
