MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013052CMakeModulespublic2012-03-18 09:192016-06-10 14:31
ReporterDaniel Franke 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
Platformx86_64OSMAC OS XOS Version10.7.3
Product VersionCMake 2.8.7 
Target VersionFixed in Version 
Summary0013052: BundleUtilities (fixup_bundle_item): location checks are too strict
DescriptionI 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?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0012382closed Kitware Robot fixup_bundle_item dies on libraries copied to a directory outside bundle directory 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-03-18 09:19Daniel FrankeNew Issue
2012-04-11 18:11Rolf Eike BeerCategoryCMake => Modules
2012-08-11 17:08David ColeRelationship addedrelated to 0012382
2012-08-11 17:08David ColeAssigned To => David Cole
2012-08-11 17:08David ColeStatusnew => assigned
2012-11-21 14:57David ColeNote Added: 0031655
2012-11-21 15:00David ColeAssigned ToDavid Cole =>
2012-11-21 15:11David ColeStatusassigned => new
2012-11-21 15:11David ColeNote Added: 0031665
2016-06-10 14:28Kitware RobotNote Added: 0042009
2016-06-10 14:28Kitware RobotStatusnew => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0031655)
David Cole   
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   
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   
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.