[cmake-developers] [CMake 0013052]: BundleUtilities (fixup_bundle_item): location checks are too strict
Mantis Bug Tracker
mantis at public.kitware.com
Sun Mar 18 09:19:03 EDT 2012
The following issue has been SUBMITTED.
======================================================================
http://public.kitware.com/Bug/view.php?id=13052
======================================================================
Reported By: Daniel Franke
Assigned To:
======================================================================
Project: CMake
Issue ID: 13052
Category: CMake
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 2012-03-18 09:19 EDT
Last Modified: 2012-03-18 09:19 EDT
======================================================================
Summary: 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?
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2012-03-18 09:19 Daniel Franke New Issue
======================================================================
More information about the cmake-developers
mailing list