Le lun. 22 oct. 2018 à 23:05, Craig Scott <craig.sc...@crascit.com> 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. >> >> May be some Mac user may shed some more light on this. >> > > You should be able to do this using install(SCRIPT) or install(CODE), > invoking the code signing through execute_process() as part of that > script/code. > I wasn't sure of that. So just to be clear do we know for sure that install(SCRIPT) install(CODE) will run after the CMake builtin-generated install scripts? The builtin generated install script for target includes stripping, so for signing to work as expect we should be sure of the execution order? Or may be you suggest not to install(TARGET) for the concerned target and write install(SCRIPT) replacement for those? Taking a step back though, I don't know what your package contains, but if > you're creating an app bundle, then you don't need CPack at all. An app > bundle is already self contained and you should be able to get it to build > with install RPATH, at which point it should find everything it needs. An > advantage of building with install RPATH is that you can also make use of > the XCODE_ATTRIBUTE target property support to set up the code signing and > have Xcode/xcodebuild drive the whole code signing process for you. It's > likely to be easier that way and is more compatible with tools like > Fastlane <https://fastlane.tools>, if you end up heading in that > direction. But if you have embedded frameworks, then yeah, you probably end > up having to do things manually yourself (CMake doesn't yet handle those > well and has no direct support for it). > > -- > Craig Scott > Melbourne, Australia > https://crascit.com > > New book released: Professional CMake: A Practical Guide > <https://crascit.com/professional-cmake/> > -- Eric
-- 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 support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
