(0029015)
Utkarsh Ayachit (administrator)
2012-08-17 13:44

commit a67c39f6044474967e7ae6fa530dede66fe53512
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Thu Aug 16 17:27:53 2012 -0400

    Fixing install rules on Mac to build ParaView.app.

    If building on apple, we will set cmake rules for ParaView such that "make
    install" will result in creation of an application bundle by default.

    The trick we play is as such:
    1. We hide the CMAKE_INSTALL_PREFIX variable at force it to a
       internal/temporary location. All generic VTK/ParaView install rules
       happily go about installing under this CMAKE_INSTALL_PREFIX location.
    2. We provide a new vairable MACOSX_APP_INSTALL_PREFIX that user can set to
       point where he wants the app bundle to be placed (default is /Applications).
    3. We set CMAKE_INSTALL_NAME_DIR to point to location of runtime libraries
       in the app bundle. Thus when the libraries are installed, cmake
       automatically cleans up the install_name paths for all shared libs that
       we built to point to a location within the app.
    4. To make packaging of plugins easier, we install plugins under a directory
       named "plugins" in the temporary CMAKE_INSTALL_PREFIX location. This just
       a simple trick to avoid having to keep track of plugins we built.
    5. Every application that builds an app, then uses the
       ParaViewBrandingInstallApp.cmake or something similar to put all the
       libraries, plugins, python files etc. within the app bundle itself.
    6. Finally, the bundle generated under the temporary location is copied over
      to the path specified by MACOSX_APP_INSTALL_PREFIX.

    In keeping with our "WE INSTALL WHAT WE BUILD" rule, this app bundle is not
    distributable to others since it does not include Qt, or other external
    dependencies. For a distributable pacakage, refer to ParaView Super-build
    instructions.

    Change-Id: Id731a00df84c1161f7ec9a13bf2c774de0b4c829
qq

(0029025)
Utkarsh Ayachit (administrator)
2012-08-17 14:27

merged in master, if applicable

(0030168)
Alan Scott (manager)
2013-01-16 22:31

Developer tag in git. Closing.

Issue History
Date Modified	Username	Field	Change
2012-08-17 13:43	Utkarsh Ayachit	New Issue
2012-08-17 13:43	Utkarsh Ayachit	Assigned To	=> Utkarsh Ayachit
2012-08-17 13:44	Utkarsh Ayachit	Topic Name	=> fix_mac_install_rules
2012-08-17 13:44	Utkarsh Ayachit	Note Added: 0029015
2012-08-17 13:44	Utkarsh Ayachit	Status	backlog => gatekeeper review
2012-08-17 13:44	Utkarsh Ayachit	Fixed in Version	=> git-next
2012-08-17 13:44	Utkarsh Ayachit	Resolution	open => fixed
2012-08-17 14:26	Utkarsh Ayachit	Fixed in Version	git-next => git-master
2012-08-17 14:27	Utkarsh Ayachit	Status	gatekeeper review => customer review
2012-08-17 14:27	Utkarsh Ayachit	Note Added: 0029025
2012-10-29 17:04	Utkarsh Ayachit	Fixed in Version	git-master => 3.98.0
2013-01-16 22:31	Alan Scott	Note Added: 0030168
2013-01-16 22:31	Alan Scott	Status	customer review => closed

Notes
(0029015) Utkarsh Ayachit (administrator) 2012-08-17 13:44	commit a67c39f6044474967e7ae6fa530dede66fe53512 Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com> Date: Thu Aug 16 17:27:53 2012 -0400 Fixing install rules on Mac to build ParaView.app. If building on apple, we will set cmake rules for ParaView such that "make install" will result in creation of an application bundle by default. The trick we play is as such: 1. We hide the CMAKE_INSTALL_PREFIX variable at force it to a internal/temporary location. All generic VTK/ParaView install rules happily go about installing under this CMAKE_INSTALL_PREFIX location. 2. We provide a new vairable MACOSX_APP_INSTALL_PREFIX that user can set to point where he wants the app bundle to be placed (default is /Applications). 3. We set CMAKE_INSTALL_NAME_DIR to point to location of runtime libraries in the app bundle. Thus when the libraries are installed, cmake automatically cleans up the install_name paths for all shared libs that we built to point to a location within the app. 4. To make packaging of plugins easier, we install plugins under a directory named "plugins" in the temporary CMAKE_INSTALL_PREFIX location. This just a simple trick to avoid having to keep track of plugins we built. 5. Every application that builds an app, then uses the ParaViewBrandingInstallApp.cmake or something similar to put all the libraries, plugins, python files etc. within the app bundle itself. 6. Finally, the bundle generated under the temporary location is copied over to the path specified by MACOSX_APP_INSTALL_PREFIX. In keeping with our "WE INSTALL WHAT WE BUILD" rule, this app bundle is not distributable to others since it does not include Qt, or other external dependencies. For a distributable pacakage, refer to ParaView Super-build instructions. Change-Id: Id731a00df84c1161f7ec9a13bf2c774de0b4c829 qq

(0029025) Utkarsh Ayachit (administrator) 2012-08-17 14:27	merged in master, if applicable

(0030168) Alan Scott (manager) 2013-01-16 22:31	Developer tag in git. Closing.

Relationships