Original Message-
> From: David Cole [mailto:david.c...@kitware.com]
> Sent: Tuesday, February 01, 2011 10:49 AM
> To: Scott Fowler
> Cc: Sean McBride; cmake@cmake.org
> Subject: Re: [CMake] Help with fixup_bundle for Mac OS - @executable_path,
> @loader_path, @rpath
>
> We
kitware.com]
Sent: Tuesday, February 01, 2011 10:49 AM
To: Scott Fowler
Cc: Sean McBride; cmake@cmake.org
Subject: Re: [CMake] Help with fixup_bundle for Mac OS - @executable_path,
@loader_path, @rpath
We only have "exepath" defined with which to make a replacement.
BundleUtilities is s
m}")
> get_filename_component(resolved_embedded_item "${resolved_embedded_item}"
> ABSOLUTE)
>
> Scott
>
> -Original Message-
> From: Sean McBride [mailto:s...@rogue-research.com]
> Sent: Tuesday, February 01, 2011 9:26 AM
> To: Scott Fowler; cmake@cmake.org
>
me_component(resolved_embedded_item "${resolved_embedded_item}"
ABSOLUTE)
Scott
-Original Message-
From: Sean McBride [mailto:s...@rogue-research.com]
Sent: Tuesday, February 01, 2011 9:26 AM
To: Scott Fowler; cmake@cmake.org
Subject: Re: [CMake] Help with fixup_bundle for Mac OS - @exec
Basically you need to implement the following cmake function:
function(gp_item_default_embedded_path_override item default_embedded_path_var)
You can set to use @executable_path or @loader_path or what ever you really
want in there.
which BundleUtilities will use if it finds it. The trick here
On Tue, 1 Feb 2011 08:39:08 -0800, Scott Fowler said:
>I have an application "Foo" which distributes a plugin for a separate
>application "Bar". My plugin is dependent on libraries distributed with
>application "Foo". When application "Bar" tries to load the plugin, the
>plugin will not load, as
I have an application "Foo" which distributes a plugin for a separate
application "Bar". My plugin is dependent on libraries distributed with
application "Foo". When application "Bar" tries to load the plugin, the plugin
will not load, as it cannot find the libraries distributed with "Foo".
A
