Hi, On Sat, Sep 28, 2013 at 12:00:04PM -0400, [email protected] wrote: > Date: Fri, 27 Sep 2013 20:20:06 +0200 > From: Eric Noulard <[email protected]> > Subject: Re: [CMake] CPack: Add PATH to .profile
> 2013/9/27 Michele Dolfi <[email protected]>: > > Using install(SCRIPT ...) in CMake the patch my own .profile, not the one of > > the user installing my app. > > Yes you want a "post-install" script. > With PackageMaker you have the > CPACK_PREFLIGHT_SCRIPT > CPACK_POSTFLIGHT_SCRIPT > > which may be used to do that but I don't know how they works > and whether if they are "selectable" at install time. Perhaps you're thinking in terms of explicit installer-side activation of execution of these scripts. But that's not necessarily necessary ;) A convincing workaround would be to have these scripts executed *unconditionally*, and then these would simply check whether a marker is available (perhaps marker file stored on a temp fs). So, IOW, the installer option would only need to have the capability of creating those marker signals somehow (in case the user selected the corresponding option), then the unconditionally executed scripts would react on those (not) existing. HTH, Andreas Mohr -- 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: http://www.cmake.org/mailman/listinfo/cmake
