Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob bob
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bobbob
  • Issues
  • #50
Closed
Open
Issue created Apr 10, 2012 by André Anjos@andre.anjos💬Owner

Solving/Simplifying the RPATH or INSTALL_DIR

Created by: anjos

Currently, to build our Ubuntu or OSX packages, we need to disable the setting of these variables as files get moved during installation using debuild or MacPorts. Here is a strategy to get rid of this annoyance:

  1. Move the library _core_array.so to the <prefix>/lib directory and version it properly
  2. Make all other python bindings depend on that instead of a library hidden at python directories
  3. Make the python bindings use the RPATH by default (this is disabled when the user passes -DCMAKE_SKIP_BUILD_RPATH=TRUE to CMake. Under OSX, have a similar mechanism that will do that for the INSTALL_DIR property.

Notes:

  1. The RPATH functionality is only required for the python bindings
  2. The python bindings only require that functionality if the libraries they depend on are not installed in a standard location.
Assignee
Assign to
Time tracking