Difference between revisions of "Documentation/Nightly/Developers/Tutorials/Debugging macOS packaging"
From Slicer Wiki
(Created page with " == Overview == The packaging on Linux and Windows consists of: (1) copying files from the build tree to a staging folder (2) creating an archive based on the staging folder...") |
|||
| Line 3: | Line 3: | ||
The packaging on Linux and Windows consists of: | The packaging on Linux and Windows consists of: | ||
| − | + | # copying files from the build tree to a staging folder | |
| − | + | # creating an archive based on the staging folder | |
macOS packaging includes an additional "fixup" step: | macOS packaging includes an additional "fixup" step: | ||
| − | + | # copying files from the build tree to a staging folder | |
| − | + | # fixup step | |
| − | + | # creating an archive based on the staging folder | |
Latest revision as of 19:01, 7 March 2019
Home < Documentation < Nightly < Developers < Tutorials < Debugging macOS packagingOverview
The packaging on Linux and Windows consists of:
- copying files from the build tree to a staging folder
- creating an archive based on the staging folder
macOS packaging includes an additional "fixup" step:
- copying files from the build tree to a staging folder
- fixup step
- creating an archive based on the staging folder
macOS file copy step
- Only plugins from external projects are copied into the staging folder
macOS "fixup" step
- Copy external project dependencies into the staging folder
- fixing up a library means replacing the rpath referencing a library using an absolute path (e.g /path/to/Slicer-SuperBuilb/VTK-build/lib/libvtkXXX-X.Y.Z.dylib) with an @rpath/ based reference (e.g @rpath/path/to/libvtkXXX-X.Y.Z.dylib)
