View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0013052 | CMake | Modules | public | 2012-03-18 09:19 | 2016-06-10 14:31 | ||||
Reporter | Daniel Franke | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | x86_64 | OS | MAC OS X | OS Version | 10.7.3 | ||||
Product Version | CMake 2.8.7 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0013052: BundleUtilities (fixup_bundle_item): location checks are too strict | ||||||||
Description | I try to build a package like this: PREFIX/foo.app /bar.app /Frameworks/baz.framework where baz.framework is used by both, foo and bar apps. Using BundleUtilities and GetPrerequisites, I finally found the possibility to override the default location of the fixed up libraries by implementing: function(gp_item_default_embedded_path_override item path) if (APPLE) set(path "@executable_path/../../../Frameworks" PARENT_SCOPE) endif (APPLE) endfunction(gp_item_default_embedded_path_override) This works, the baz frameworks end up in PREFIX/Frameworks, but the fixup step fails because the framework is not within the .app directory: message(FATAL_ERROR "cannot fixup an item that is not in the bundle...") Where is the point that GetPrerequisites allows a user defined location of frameworks - which may be outside the .app directory - and have BundleUtilities insist on a location inside the same? | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | ||||||
|
Relationships |
Notes | |
(0031655) David Cole (manager) 2012-11-21 14:57 |
Un-assigning bugs that are not on the active roadmap, which no developers are actively working on for the CMake 2.8.11 release. If one gets put back on the roadmap, re-assign it appropriately at that time. |
(0031665) David Cole (manager) 2012-11-21 15:11 |
Re-setting status back to "new" for bugs that are "assigned" but not assigned to a specific developer. When/if these bugs go back on the roadmap for a specific version, assignment to an appropriate developer should take place then... |
(0042009) Kitware Robot (administrator) 2016-06-10 14:28 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2012-03-18 09:19 | Daniel Franke | New Issue | |
2012-04-11 18:11 | Rolf Eike Beer | Category | CMake => Modules |
2012-08-11 17:08 | David Cole | Relationship added | related to 0012382 |
2012-08-11 17:08 | David Cole | Assigned To | => David Cole |
2012-08-11 17:08 | David Cole | Status | new => assigned |
2012-11-21 14:57 | David Cole | Note Added: 0031655 | |
2012-11-21 15:00 | David Cole | Assigned To | David Cole => |
2012-11-21 15:11 | David Cole | Status | assigned => new |
2012-11-21 15:11 | David Cole | Note Added: 0031665 | |
2016-06-10 14:28 | Kitware Robot | Note Added: 0042009 | |
2016-06-10 14:28 | Kitware Robot | Status | new => resolved |
2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |