Attached a small patch for the fixup_bundle documentation which would helped me a lot when I've stared using fixup_bundle.
Peter
diff --git a/Modules/BundleUtilities.cmake b/Modules/BundleUtilities.cmake index 44f2c20..6811fb6 100644 --- a/Modules/BundleUtilities.cmake +++ b/Modules/BundleUtilities.cmake @@ -23,14 +23,25 @@ # PARENT_SCOPE. Also depends on GetPrerequisites.cmake. # # FIXUP_BUNDLE(<app> <libs> <dirs>) +# <app> one executables or library +# <libs> executables and libraries which <app> not directly links to +# <dirs> additional search pathes for the dependencies of <app> and <libs> +# # Fix up a bundle in-place and make it standalone, such that it can be # drag-n-drop copied to another machine and run on that machine as long as all # of the system libraries are compatible. # +# The whole concept of fixup_bundle is based on the assumption that there is a +# direcrory(bundle) containing some set of executable files (*.exes and *.dll/dylib/so) +# to begin with. All other libraries these executable files depends on will be copied +# by fixup_bundle into the bundle. fixup_bundle could only detect dependencies which +# are hardcoded into the executables and which could be found by GetPrerequisites. +# Therefore you always have to pass plugins as <libs> parameter to fixup_bundle, +# because by definition applications do know nothing about the existance of a +# concrete plugin. +# # If you pass plugins to fixup_bundle as the libs parameter, you should install -# them or copy them into the bundle before calling fixup_bundle. The "libs" -# parameter is a list of libraries that must be fixed up, but that cannot be -# determined by otool output analysis. (i.e., plugins) +# them or copy them into the bundle before calling fixup_bundle. # # Gather all the keys for all the executables and libraries in a bundle, and # then, for each key, copy each prerequisite into the bundle. Then fix each one
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
