Maybe try @rpath or @loader_path?  I imagine @executable_path is
resolving to the VST Host's path.

Check out:

https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath

On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh  wrote:
> Any Xcode people out who might be able to assist me with this? I'm trying to
> bundle Csound into my apps by including the framework within the app bundle.
> To do so I use install_name_tool like this:
>
> install_name_tool -id
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> \
>
> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>
> This works fine for the main Cabbage app bundle, but doesn't work for VST
> bundles. I don't get it because my VSTs bawk out with the following error:
>
> Attempting to load VST:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> 262): Library not loaded:
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>   Referenced from:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>   Reason: image not found
>
> But a simple "show package contents" within the .VST bundle shows that the
> library is located at
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64

Hmmm. No when I open Cabbage on a machine that doesn't have Csound installed it crashes out with an error about libsndfile. Do I have to use the install_name_tool with every library within the Csound framework too?

On 13 October 2015 at 18:20, Rory Walsh <rorywalsh@ear.ie> wrote:

Brilliant. loader_path did the trick :)

On 13 October 2015 at 16:14, Rory Walsh <rorywalsh@ear.ie> wrote:

Thanks Steven. I'll give it a go.

On 13 October 2015 at 16:11, Steven Yi <stevenyi@gmail.com> wrote:

Maybe try @rpath or @loader_path?  I imagine @executable_path is
resolving to the VST Host's path.

Check out:

https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath

On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> Any Xcode people out who might be able to assist me with this? I'm trying to
> bundle Csound into my apps by including the framework within the app bundle.
> To do so I use install_name_tool like this:
>
> install_name_tool -id
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> \
>
> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>
> This works fine for the main Cabbage app bundle, but doesn't work for VST
> bundles. I don't get it because my VSTs bawk out with the following error:
>
> Attempting to load VST:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> 262): Library not loaded:
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>   Referenced from:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>   Reason: image not found
>
> But a simple "show package contents" within the .VST bundle shows that the
> library is located at
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> as it should be? Any ideas? Xcode drives me nuts.

Yikes. Good to know.

On 15 October 2015 at 15:03, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

yes.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 15 Oct 2015, at 12:32, Rory Walsh <rorywalsh@EAR.IE> wrote:

Hmmm. No when I open Cabbage on a machine that doesn't have Csound installed it crashes out with an error about libsndfile. Do I have to use the install_name_tool with every library within the Csound framework too?

On 13 October 2015 at 18:20, Rory Walsh <rorywalsh@ear.ie> wrote:

Brilliant. loader_path did the trick :)

On 13 October 2015 at 16:14, Rory Walsh <rorywalsh@ear.ie> wrote:

Thanks Steven. I'll give it a go.

On 13 October 2015 at 16:11, Steven Yi <stevenyi@gmail.com> wrote:

Maybe try @rpath or @loader_path?  I imagine @executable_path is
resolving to the VST Host's path.

Check out:

https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath

On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> Any Xcode people out who might be able to assist me with this? I'm trying to
> bundle Csound into my apps by including the framework within the app bundle.
> To do so I use install_name_tool like this:
>
> install_name_tool -id
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> \
>
> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>
> This works fine for the main Cabbage app bundle, but doesn't work for VST
> bundles. I don't get it because my VSTs bawk out with the following error:
>
> Attempting to load VST:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> 262): Library not loaded:
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>   Referenced from:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>   Reason: image not found
>
> But a simple "show package contents" within the .VST bundle shows that the
> library is located at
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> as it should be? Any ideas? Xcode drives me nuts.

Yikes. Good to know.

On 15 October 2015 at 15:03, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

yes.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 15 Oct 2015, at 12:32, Rory Walsh <rorywalsh@EAR.IE> wrote:

Hmmm. No when I open Cabbage on a machine that doesn't have Csound installed it crashes out with an error about libsndfile. Do I have to use the install_name_tool with every library within the Csound framework too?

On 13 October 2015 at 18:20, Rory Walsh <rorywalsh@ear.ie> wrote:

Brilliant. loader_path did the trick :)

On 13 October 2015 at 16:14, Rory Walsh <rorywalsh@ear.ie> wrote:

Thanks Steven. I'll give it a go.

On 13 October 2015 at 16:11, Steven Yi <stevenyi@gmail.com> wrote:

Maybe try @rpath or @loader_path?  I imagine @executable_path is
resolving to the VST Host's path.

Check out:

https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath

On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh <rorywalsh@ear.ie> wrote:
> Any Xcode people out who might be able to assist me with this? I'm trying to
> bundle Csound into my apps by including the framework within the app bundle.
> To do so I use install_name_tool like this:
>
> install_name_tool -id
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> \
>
> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>
> This works fine for the main Cabbage app bundle, but doesn't work for VST
> bundles. I don't get it because my VSTs bawk out with the following error:
>
> Attempting to load VST:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> 262): Library not loaded:
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>   Referenced from:
> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>   Reason: image not found
>
> But a simple "show package contents" within the .VST bundle shows that the
> library is located at
> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> as it should be? Any ideas? Xcode drives me nuts.

There are two places it is normally installed:

1) the installer places it in /Library/Frameworks/CsoundLib64.framework
2) the cmake install method places it in ~/Library/Frameworks/CsoundLib64.framework

Also you might have support libs hanging in /usr/local/lib

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
> 
> In order to know if this works I have to recreate the same conditions as on a clean machine without Csound. But I can't seem to do that even when I remove the CsoundLib.framework from Library/Frameworks. Is there anything else I can do to make sure Csound is completely removed from the system? The .app bundle that was causing problems on a fresh machine runs fine on mine? And I haven't ran any of the install_name_tool stuff yet.
> 
> On 15 October 2015 at 13:54, Rory Walsh  wrote:
> That's great. Thanks. 
> 
> On 15 October 2015 at 15:43, Victor Lazzarini  wrote:
> have a look at the build-release.sh script in the installer/macosx/ subdirectory.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
> 
>> Yikes. Good to know. 
>> 
>> On 15 October 2015 at 15:03, Victor Lazzarini  wrote:
>> yes.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
>> 
>>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound installed it crashes out with an error about libsndfile. Do I have to use the install_name_tool with every library within the Csound framework too? 
>>> 
>>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
>>> Brilliant. loader_path did the trick :) 
>>> 
>>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
>>> Thanks Steven. I'll give it a go. 
>>> 
>>> On 13 October 2015 at 16:11, Steven Yi  wrote:
>>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
>>> resolving to the VST Host's path.
>>> 
>>> Check out:
>>> 
>>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
>>> 
>>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh  wrote:
>>> > Any Xcode people out who might be able to assist me with this? I'm trying to
>>> > bundle Csound into my apps by including the framework within the app bundle.
>>> > To do so I use install_name_tool like this:
>>> >
>>> > install_name_tool -id
>>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> > \
>>> >
>>> > /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >
>>> > This works fine for the main Cabbage app bundle, but doesn't work for VST
>>> > bundles. I don't get it because my VSTs bawk out with the following error:
>>> >
>>> > Attempting to load VST:
>>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
>>> > 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
>>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
>>> > dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
>>> > 262): Library not loaded:
>>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >   Referenced from:
>>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>>> >   Reason: image not found
>>> >
>>> > But a simple "show package contents" within the .VST bundle shows that the
>>> > library is located at
>>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> > as it should be? Any ideas? Xcode drives me nuts.
>>> 
>>> 
>>> 
>> 
> 

Are you using install_name_tool with -change on the libraries that
link to libsndfile?

On Thu, Oct 15, 2015 at 11:11 AM, Rory Walsh  wrote:
> Seems like my luck ran out with this one. On the off chance someone can
> help, I'll describe what I'm at. I've placed the libsndfile.1.dylib into the
> same folder as the CsoundLib64 binary in my custom Csound framework. I run
> this command. According to what spare information I can find, @loader_path
> will get expanded to the full path of the loading binary, in this case
> Csound64Lib.
>
> install_name_tool -id @loader_path/libs/libsndfile.1.dylib \
>
> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/libs/libsndfile.1.dylib
>
> When I build Cabbage xcode bundles the Csound framework into the app bundle.
> But Csound can't find the libsndfile library when it's first called. I'll
> keep digging..
>
> On 15 October 2015 at 15:00, Rory Walsh  wrote:
>>
>> Bingo. They were hiding in /usr/loca/lib
>>
>> On 15 October 2015 at 14:55, Victor Lazzarini 
>> wrote:
>>>
>>> There are two places it is normally installed:
>>>
>>> 1) the installer places it in /Library/Frameworks/CsoundLib64.framework
>>> 2) the cmake install method places it in
>>> ~/Library/Frameworks/CsoundLib64.framework
>>>
>>> Also you might have support libs hanging in /usr/local/lib
>>>
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>> > On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
>>> >
>>> > In order to know if this works I have to recreate the same conditions
>>> > as on a clean machine without Csound. But I can't seem to do that even when
>>> > I remove the CsoundLib.framework from Library/Frameworks. Is there anything
>>> > else I can do to make sure Csound is completely removed from the system? The
>>> > .app bundle that was causing problems on a fresh machine runs fine on mine?
>>> > And I haven't ran any of the install_name_tool stuff yet.
>>> >
>>> > On 15 October 2015 at 13:54, Rory Walsh  wrote:
>>> > That's great. Thanks.
>>> >
>>> > On 15 October 2015 at 15:43, Victor Lazzarini
>>> >  wrote:
>>> > have a look at the build-release.sh script in the installer/macosx/
>>> > subdirectory.
>>> >
>>> > Victor Lazzarini
>>> > Dean of Arts, Celtic Studies, and Philosophy
>>> > Maynooth University
>>> > Ireland
>>> >
>>> > On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
>>> >
>>> >> Yikes. Good to know.
>>> >>
>>> >> On 15 October 2015 at 15:03, Victor Lazzarini
>>> >>  wrote:
>>> >> yes.
>>> >>
>>> >> Victor Lazzarini
>>> >> Dean of Arts, Celtic Studies, and Philosophy
>>> >> Maynooth University
>>> >> Ireland
>>> >>
>>> >> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
>>> >>
>>> >>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound
>>> >>> installed it crashes out with an error about libsndfile. Do I have to use
>>> >>> the install_name_tool with every library within the Csound framework too?
>>> >>>
>>> >>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
>>> >>> Brilliant. loader_path did the trick :)
>>> >>>
>>> >>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
>>> >>> Thanks Steven. I'll give it a go.
>>> >>>
>>> >>> On 13 October 2015 at 16:11, Steven Yi  wrote:
>>> >>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
>>> >>> resolving to the VST Host's path.
>>> >>>
>>> >>> Check out:
>>> >>>
>>> >>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
>>> >>>
>>> >>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh 
>>> >>> wrote:
>>> >>> > Any Xcode people out who might be able to assist me with this? I'm
>>> >>> > trying to
>>> >>> > bundle Csound into my apps by including the framework within the
>>> >>> > app bundle.
>>> >>> > To do so I use install_name_tool like this:
>>> >>> >
>>> >>> > install_name_tool -id
>>> >>> >
>>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >>> > \
>>> >>> >
>>> >>> >
>>> >>> > /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >>> >
>>> >>> > This works fine for the main Cabbage app bundle, but doesn't work
>>> >>> > for VST
>>> >>> > bundles. I don't get it because my VSTs bawk out with the following
>>> >>> > error:
>>> >>> >
>>> >>> > Attempting to load VST:
>>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
>>> >>> > 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
>>> >>> >
>>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
>>> >>> >
>>> >>> > dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
>>> >>> > 262): Library not loaded:
>>> >>> >
>>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >>> >   Referenced from:
>>> >>> >
>>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>>> >>> >   Reason: image not found
>>> >>> >
>>> >>> > But a simple "show package contents" within the .VST bundle shows
>>> >>> > that the
>>> >>> > library is located at
>>> >>> >
>>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>> >>> > as it should be? Any ideas? Xcode drives me nuts.
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> >
>>> >
>>
>>

I think you use -id on the library that is linked to, and use -change
on the library that is on the executable or library that is linked
from.  (I've never really understood why libraries have id's on
OSX...)

On Thu, Oct 15, 2015 at 11:29 AM, Rory Walsh  wrote:
> Nope. I've been using it with -id? I guess I should use -change instead?
>
> On 15 October 2015 at 16:29, Steven Yi  wrote:
>>
>> Are you using install_name_tool with -change on the libraries that
>> link to libsndfile?
>>
>> On Thu, Oct 15, 2015 at 11:11 AM, Rory Walsh  wrote:
>> > Seems like my luck ran out with this one. On the off chance someone can
>> > help, I'll describe what I'm at. I've placed the libsndfile.1.dylib into
>> > the
>> > same folder as the CsoundLib64 binary in my custom Csound framework. I
>> > run
>> > this command. According to what spare information I can find,
>> > @loader_path
>> > will get expanded to the full path of the loading binary, in this case
>> > Csound64Lib.
>> >
>> > install_name_tool -id @loader_path/libs/libsndfile.1.dylib \
>> >
>> >
>> > /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/libs/libsndfile.1.dylib
>> >
>> > When I build Cabbage xcode bundles the Csound framework into the app
>> > bundle.
>> > But Csound can't find the libsndfile library when it's first called.
>> > I'll
>> > keep digging..
>> >
>> > On 15 October 2015 at 15:00, Rory Walsh  wrote:
>> >>
>> >> Bingo. They were hiding in /usr/loca/lib
>> >>
>> >> On 15 October 2015 at 14:55, Victor Lazzarini
>> >> 
>> >> wrote:
>> >>>
>> >>> There are two places it is normally installed:
>> >>>
>> >>> 1) the installer places it in
>> >>> /Library/Frameworks/CsoundLib64.framework
>> >>> 2) the cmake install method places it in
>> >>> ~/Library/Frameworks/CsoundLib64.framework
>> >>>
>> >>> Also you might have support libs hanging in /usr/local/lib
>> >>>
>> >>> ========================
>> >>> Dr Victor Lazzarini
>> >>> Dean of Arts, Celtic Studies and Philosophy,
>> >>> Maynooth University,
>> >>> Maynooth, Co Kildare, Ireland
>> >>> Tel: 00 353 7086936
>> >>> Fax: 00 353 1 7086952
>> >>>
>> >>> > On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
>> >>> >
>> >>> > In order to know if this works I have to recreate the same
>> >>> > conditions
>> >>> > as on a clean machine without Csound. But I can't seem to do that
>> >>> > even when
>> >>> > I remove the CsoundLib.framework from Library/Frameworks. Is there
>> >>> > anything
>> >>> > else I can do to make sure Csound is completely removed from the
>> >>> > system? The
>> >>> > .app bundle that was causing problems on a fresh machine runs fine
>> >>> > on mine?
>> >>> > And I haven't ran any of the install_name_tool stuff yet.
>> >>> >
>> >>> > On 15 October 2015 at 13:54, Rory Walsh  wrote:
>> >>> > That's great. Thanks.
>> >>> >
>> >>> > On 15 October 2015 at 15:43, Victor Lazzarini
>> >>> >  wrote:
>> >>> > have a look at the build-release.sh script in the installer/macosx/
>> >>> > subdirectory.
>> >>> >
>> >>> > Victor Lazzarini
>> >>> > Dean of Arts, Celtic Studies, and Philosophy
>> >>> > Maynooth University
>> >>> > Ireland
>> >>> >
>> >>> > On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
>> >>> >
>> >>> >> Yikes. Good to know.
>> >>> >>
>> >>> >> On 15 October 2015 at 15:03, Victor Lazzarini
>> >>> >>  wrote:
>> >>> >> yes.
>> >>> >>
>> >>> >> Victor Lazzarini
>> >>> >> Dean of Arts, Celtic Studies, and Philosophy
>> >>> >> Maynooth University
>> >>> >> Ireland
>> >>> >>
>> >>> >> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
>> >>> >>
>> >>> >>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound
>> >>> >>> installed it crashes out with an error about libsndfile. Do I have
>> >>> >>> to use
>> >>> >>> the install_name_tool with every library within the Csound
>> >>> >>> framework too?
>> >>> >>>
>> >>> >>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
>> >>> >>> Brilliant. loader_path did the trick :)
>> >>> >>>
>> >>> >>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
>> >>> >>> Thanks Steven. I'll give it a go.
>> >>> >>>
>> >>> >>> On 13 October 2015 at 16:11, Steven Yi  wrote:
>> >>> >>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
>> >>> >>> resolving to the VST Host's path.
>> >>> >>>
>> >>> >>> Check out:
>> >>> >>>
>> >>> >>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
>> >>> >>>
>> >>> >>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh 
>> >>> >>> wrote:
>> >>> >>> > Any Xcode people out who might be able to assist me with this?
>> >>> >>> > I'm
>> >>> >>> > trying to
>> >>> >>> > bundle Csound into my apps by including the framework within the
>> >>> >>> > app bundle.
>> >>> >>> > To do so I use install_name_tool like this:
>> >>> >>> >
>> >>> >>> > install_name_tool -id
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>> >>> >>> > \
>> >>> >>> >
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>> >>> >>> >
>> >>> >>> > This works fine for the main Cabbage app bundle, but doesn't
>> >>> >>> > work
>> >>> >>> > for VST
>> >>> >>> > bundles. I don't get it because my VSTs bawk out with the
>> >>> >>> > following
>> >>> >>> > error:
>> >>> >>> >
>> >>> >>> > Attempting to load VST:
>> >>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
>> >>> >>> > 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
>> >>> >>> > 262): Library not loaded:
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>> >>> >>> >   Referenced from:
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>> >>> >>> >   Reason: image not found
>> >>> >>> >
>> >>> >>> > But a simple "show package contents" within the .VST bundle
>> >>> >>> > shows
>> >>> >>> > that the
>> >>> >>> > library is located at
>> >>> >>> >
>> >>> >>> >
>> >>> >>> > @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>> >>> >>> > as it should be? Any ideas? Xcode drives me nuts.
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> >>> >>
>> >>> >
>> >>> >
>> >>
>> >>
>> >
>

you need to do both:

1) change the ID for each library to reflect the location

2) change the link on each loader exec or lib to point to the correct lib location

Use otool -L to check it is correct.

Again if you look in that script you will see how it is done.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 15 Oct 2015, at 16:34, Steven Yi  wrote:
> 
> I think you use -id on the library that is linked to, and use -change
> on the library that is on the executable or library that is linked
> from.  (I've never really understood why libraries have id's on
> OSX...)
> 
>> On Thu, Oct 15, 2015 at 11:29 AM, Rory Walsh  wrote:
>> Nope. I've been using it with -id? I guess I should use -change instead?
>> 
>>> On 15 October 2015 at 16:29, Steven Yi  wrote:
>>> 
>>> Are you using install_name_tool with -change on the libraries that
>>> link to libsndfile?
>>> 
>>>> On Thu, Oct 15, 2015 at 11:11 AM, Rory Walsh  wrote:
>>>> Seems like my luck ran out with this one. On the off chance someone can
>>>> help, I'll describe what I'm at. I've placed the libsndfile.1.dylib into
>>>> the
>>>> same folder as the CsoundLib64 binary in my custom Csound framework. I
>>>> run
>>>> this command. According to what spare information I can find,
>>>> @loader_path
>>>> will get expanded to the full path of the loading binary, in this case
>>>> Csound64Lib.
>>>> 
>>>> install_name_tool -id @loader_path/libs/libsndfile.1.dylib \
>>>> 
>>>> 
>>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/libs/libsndfile.1.dylib
>>>> 
>>>> When I build Cabbage xcode bundles the Csound framework into the app
>>>> bundle.
>>>> But Csound can't find the libsndfile library when it's first called.
>>>> I'll
>>>> keep digging..
>>>> 
>>>>> On 15 October 2015 at 15:00, Rory Walsh  wrote:
>>>>> 
>>>>> Bingo. They were hiding in /usr/loca/lib
>>>>> 
>>>>> On 15 October 2015 at 14:55, Victor Lazzarini
>>>>> 
>>>>> wrote:
>>>>>> 
>>>>>> There are two places it is normally installed:
>>>>>> 
>>>>>> 1) the installer places it in
>>>>>> /Library/Frameworks/CsoundLib64.framework
>>>>>> 2) the cmake install method places it in
>>>>>> ~/Library/Frameworks/CsoundLib64.framework
>>>>>> 
>>>>>> Also you might have support libs hanging in /usr/local/lib
>>>>>> 
>>>>>> ========================
>>>>>> Dr Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>> 
>>>>>>> On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
>>>>>>> 
>>>>>>> In order to know if this works I have to recreate the same
>>>>>>> conditions
>>>>>>> as on a clean machine without Csound. But I can't seem to do that
>>>>>>> even when
>>>>>>> I remove the CsoundLib.framework from Library/Frameworks. Is there
>>>>>>> anything
>>>>>>> else I can do to make sure Csound is completely removed from the
>>>>>>> system? The
>>>>>>> .app bundle that was causing problems on a fresh machine runs fine
>>>>>>> on mine?
>>>>>>> And I haven't ran any of the install_name_tool stuff yet.
>>>>>>> 
>>>>>>> On 15 October 2015 at 13:54, Rory Walsh  wrote:
>>>>>>> That's great. Thanks.
>>>>>>> 
>>>>>>> On 15 October 2015 at 15:43, Victor Lazzarini
>>>>>>>  wrote:
>>>>>>> have a look at the build-release.sh script in the installer/macosx/
>>>>>>> subdirectory.
>>>>>>> 
>>>>>>> Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> Maynooth University
>>>>>>> Ireland
>>>>>>> 
>>>>>>>> On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
>>>>>>>> 
>>>>>>>> Yikes. Good to know.
>>>>>>>> 
>>>>>>>> On 15 October 2015 at 15:03, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>> yes.
>>>>>>>> 
>>>>>>>> Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>> Maynooth University
>>>>>>>> Ireland
>>>>>>>> 
>>>>>>>>> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
>>>>>>>>> 
>>>>>>>>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound
>>>>>>>>> installed it crashes out with an error about libsndfile. Do I have
>>>>>>>>> to use
>>>>>>>>> the install_name_tool with every library within the Csound
>>>>>>>>> framework too?
>>>>>>>>> 
>>>>>>>>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
>>>>>>>>> Brilliant. loader_path did the trick :)
>>>>>>>>> 
>>>>>>>>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
>>>>>>>>> Thanks Steven. I'll give it a go.
>>>>>>>>> 
>>>>>>>>> On 13 October 2015 at 16:11, Steven Yi  wrote:
>>>>>>>>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
>>>>>>>>> resolving to the VST Host's path.
>>>>>>>>> 
>>>>>>>>> Check out:
>>>>>>>>> 
>>>>>>>>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
>>>>>>>>> 
>>>>>>>>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh 
>>>>>>>>> wrote:
>>>>>>>>>> Any Xcode people out who might be able to assist me with this?
>>>>>>>>>> I'm
>>>>>>>>>> trying to
>>>>>>>>>> bundle Csound into my apps by including the framework within the
>>>>>>>>>> app bundle.
>>>>>>>>>> To do so I use install_name_tool like this:
>>>>>>>>>> 
>>>>>>>>>> install_name_tool -id
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>>>>>>>>> \
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>>>>>>>>> 
>>>>>>>>>> This works fine for the main Cabbage app bundle, but doesn't
>>>>>>>>>> work
>>>>>>>>>> for VST
>>>>>>>>>> bundles. I don't get it because my VSTs bawk out with the
>>>>>>>>>> following
>>>>>>>>>> error:
>>>>>>>>>> 
>>>>>>>>>> Attempting to load VST:
>>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
>>>>>>>>>> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
>>>>>>>>>> 262): Library not loaded:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>>>>>>>>>  Referenced from:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
>>>>>>>>>>  Reason: image not found
>>>>>>>>>> 
>>>>>>>>>> But a simple "show package contents" within the .VST bundle
>>>>>>>>>> shows
>>>>>>>>>> that the
>>>>>>>>>> library is located at
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
>>>>>>>>>> as it should be? Any ideas? Xcode drives me nuts.
>> 

Can you try running otool -L …  and see what it says?
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 Oct 2015, at 16:31, Rory Walsh  wrote:
> 
> Hi guys. I've lifted what I needed from that script and tried to put together my own but I'm still get an error about libsndfile. This is my script:
> https://github.com/rorywalsh/cabbage/blob/develop/Builds/MacOSX/relink.sh
> I'm rather hoping there is an obvious problem that you can spot? 
> 
> On 15 October 2015 at 17:29, Rory Walsh  wrote:
> Thanks guys. I'll take another crack at it tomorrow.
> 
> On 15 October 2015 at 19:06, Victor Lazzarini  wrote:
> you need to do both:
> 
> 1) change the ID for each library to reflect the location
> 
> 2) change the link on each loader exec or lib to point to the correct lib location
> 
> Use otool -L to check it is correct.
> 
> Again if you look in that script you will see how it is done.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> > On 15 Oct 2015, at 16:34, Steven Yi  wrote:
> >
> > I think you use -id on the library that is linked to, and use -change
> > on the library that is on the executable or library that is linked
> > from.  (I've never really understood why libraries have id's on
> > OSX...)
> >
> >> On Thu, Oct 15, 2015 at 11:29 AM, Rory Walsh  wrote:
> >> Nope. I've been using it with -id? I guess I should use -change instead?
> >>
> >>> On 15 October 2015 at 16:29, Steven Yi  wrote:
> >>>
> >>> Are you using install_name_tool with -change on the libraries that
> >>> link to libsndfile?
> >>>
> >>>> On Thu, Oct 15, 2015 at 11:11 AM, Rory Walsh  wrote:
> >>>> Seems like my luck ran out with this one. On the off chance someone can
> >>>> help, I'll describe what I'm at. I've placed the libsndfile.1.dylib into
> >>>> the
> >>>> same folder as the CsoundLib64 binary in my custom Csound framework. I
> >>>> run
> >>>> this command. According to what spare information I can find,
> >>>> @loader_path
> >>>> will get expanded to the full path of the loading binary, in this case
> >>>> Csound64Lib.
> >>>>
> >>>> install_name_tool -id @loader_path/libs/libsndfile.1.dylib \
> >>>>
> >>>>
> >>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/libs/libsndfile.1.dylib
> >>>>
> >>>> When I build Cabbage xcode bundles the Csound framework into the app
> >>>> bundle.
> >>>> But Csound can't find the libsndfile library when it's first called.
> >>>> I'll
> >>>> keep digging..
> >>>>
> >>>>> On 15 October 2015 at 15:00, Rory Walsh  wrote:
> >>>>>
> >>>>> Bingo. They were hiding in /usr/loca/lib
> >>>>>
> >>>>> On 15 October 2015 at 14:55, Victor Lazzarini
> >>>>> 
> >>>>> wrote:
> >>>>>>
> >>>>>> There are two places it is normally installed:
> >>>>>>
> >>>>>> 1) the installer places it in
> >>>>>> /Library/Frameworks/CsoundLib64.framework
> >>>>>> 2) the cmake install method places it in
> >>>>>> ~/Library/Frameworks/CsoundLib64.framework
> >>>>>>
> >>>>>> Also you might have support libs hanging in /usr/local/lib
> >>>>>>
> >>>>>> ========================
> >>>>>> Dr Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>>> On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
> >>>>>>>
> >>>>>>> In order to know if this works I have to recreate the same
> >>>>>>> conditions
> >>>>>>> as on a clean machine without Csound. But I can't seem to do that
> >>>>>>> even when
> >>>>>>> I remove the CsoundLib.framework from Library/Frameworks. Is there
> >>>>>>> anything
> >>>>>>> else I can do to make sure Csound is completely removed from the
> >>>>>>> system? The
> >>>>>>> .app bundle that was causing problems on a fresh machine runs fine
> >>>>>>> on mine?
> >>>>>>> And I haven't ran any of the install_name_tool stuff yet.
> >>>>>>>
> >>>>>>> On 15 October 2015 at 13:54, Rory Walsh  wrote:
> >>>>>>> That's great. Thanks.
> >>>>>>>
> >>>>>>> On 15 October 2015 at 15:43, Victor Lazzarini
> >>>>>>>  wrote:
> >>>>>>> have a look at the build-release.sh script in the installer/macosx/
> >>>>>>> subdirectory.
> >>>>>>>
> >>>>>>> Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies, and Philosophy
> >>>>>>> Maynooth University
> >>>>>>> Ireland
> >>>>>>>
> >>>>>>>> On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
> >>>>>>>>
> >>>>>>>> Yikes. Good to know.
> >>>>>>>>
> >>>>>>>> On 15 October 2015 at 15:03, Victor Lazzarini
> >>>>>>>>  wrote:
> >>>>>>>> yes.
> >>>>>>>>
> >>>>>>>> Victor Lazzarini
> >>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
> >>>>>>>> Maynooth University
> >>>>>>>> Ireland
> >>>>>>>>
> >>>>>>>>> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
> >>>>>>>>>
> >>>>>>>>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound
> >>>>>>>>> installed it crashes out with an error about libsndfile. Do I have
> >>>>>>>>> to use
> >>>>>>>>> the install_name_tool with every library within the Csound
> >>>>>>>>> framework too?
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
> >>>>>>>>> Brilliant. loader_path did the trick :)
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
> >>>>>>>>> Thanks Steven. I'll give it a go.
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 16:11, Steven Yi  wrote:
> >>>>>>>>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
> >>>>>>>>> resolving to the VST Host's path.
> >>>>>>>>>
> >>>>>>>>> Check out:
> >>>>>>>>>
> >>>>>>>>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
> >>>>>>>>>
> >>>>>>>>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh 
> >>>>>>>>> wrote:
> >>>>>>>>>> Any Xcode people out who might be able to assist me with this?
> >>>>>>>>>> I'm
> >>>>>>>>>> trying to
> >>>>>>>>>> bundle Csound into my apps by including the framework within the
> >>>>>>>>>> app bundle.
> >>>>>>>>>> To do so I use install_name_tool like this:
> >>>>>>>>>>
> >>>>>>>>>> install_name_tool -id
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>> \
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>>
> >>>>>>>>>> This works fine for the main Cabbage app bundle, but doesn't
> >>>>>>>>>> work
> >>>>>>>>>> for VST
> >>>>>>>>>> bundles. I don't get it because my VSTs bawk out with the
> >>>>>>>>>> following
> >>>>>>>>>> error:
> >>>>>>>>>>
> >>>>>>>>>> Attempting to load VST:
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> >>>>>>>>>> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> >>>>>>>>>> 262): Library not loaded:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>>  Referenced from:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
> >>>>>>>>>>  Reason: image not found
> >>>>>>>>>>
> >>>>>>>>>> But a simple "show package contents" within the .VST bundle
> >>>>>>>>>> shows
> >>>>>>>>>> that the
> >>>>>>>>>> library is located at
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>> as it should be? Any ideas? Xcode drives me nuts.
> >>
> >>
> 

Typo:

@exectuble_path

should be

@executable_path
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 16 Oct 2015, at 16:31, Rory Walsh  wrote:
> 
> Hi guys. I've lifted what I needed from that script and tried to put together my own but I'm still get an error about libsndfile. This is my script:
> https://github.com/rorywalsh/cabbage/blob/develop/Builds/MacOSX/relink.sh
> I'm rather hoping there is an obvious problem that you can spot? 
> 
> On 15 October 2015 at 17:29, Rory Walsh  wrote:
> Thanks guys. I'll take another crack at it tomorrow.
> 
> On 15 October 2015 at 19:06, Victor Lazzarini  wrote:
> you need to do both:
> 
> 1) change the ID for each library to reflect the location
> 
> 2) change the link on each loader exec or lib to point to the correct lib location
> 
> Use otool -L to check it is correct.
> 
> Again if you look in that script you will see how it is done.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
> > On 15 Oct 2015, at 16:34, Steven Yi  wrote:
> >
> > I think you use -id on the library that is linked to, and use -change
> > on the library that is on the executable or library that is linked
> > from.  (I've never really understood why libraries have id's on
> > OSX...)
> >
> >> On Thu, Oct 15, 2015 at 11:29 AM, Rory Walsh  wrote:
> >> Nope. I've been using it with -id? I guess I should use -change instead?
> >>
> >>> On 15 October 2015 at 16:29, Steven Yi  wrote:
> >>>
> >>> Are you using install_name_tool with -change on the libraries that
> >>> link to libsndfile?
> >>>
> >>>> On Thu, Oct 15, 2015 at 11:11 AM, Rory Walsh  wrote:
> >>>> Seems like my luck ran out with this one. On the off chance someone can
> >>>> help, I'll describe what I'm at. I've placed the libsndfile.1.dylib into
> >>>> the
> >>>> same folder as the CsoundLib64 binary in my custom Csound framework. I
> >>>> run
> >>>> this command. According to what spare information I can find,
> >>>> @loader_path
> >>>> will get expanded to the full path of the loading binary, in this case
> >>>> Csound64Lib.
> >>>>
> >>>> install_name_tool -id @loader_path/libs/libsndfile.1.dylib \
> >>>>
> >>>>
> >>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/libs/libsndfile.1.dylib
> >>>>
> >>>> When I build Cabbage xcode bundles the Csound framework into the app
> >>>> bundle.
> >>>> But Csound can't find the libsndfile library when it's first called.
> >>>> I'll
> >>>> keep digging..
> >>>>
> >>>>> On 15 October 2015 at 15:00, Rory Walsh  wrote:
> >>>>>
> >>>>> Bingo. They were hiding in /usr/loca/lib
> >>>>>
> >>>>> On 15 October 2015 at 14:55, Victor Lazzarini
> >>>>> 
> >>>>> wrote:
> >>>>>>
> >>>>>> There are two places it is normally installed:
> >>>>>>
> >>>>>> 1) the installer places it in
> >>>>>> /Library/Frameworks/CsoundLib64.framework
> >>>>>> 2) the cmake install method places it in
> >>>>>> ~/Library/Frameworks/CsoundLib64.framework
> >>>>>>
> >>>>>> Also you might have support libs hanging in /usr/local/lib
> >>>>>>
> >>>>>> ========================
> >>>>>> Dr Victor Lazzarini
> >>>>>> Dean of Arts, Celtic Studies and Philosophy,
> >>>>>> Maynooth University,
> >>>>>> Maynooth, Co Kildare, Ireland
> >>>>>> Tel: 00 353 7086936
> >>>>>> Fax: 00 353 1 7086952
> >>>>>>
> >>>>>>> On 15 Oct 2015, at 14:51, Rory Walsh  wrote:
> >>>>>>>
> >>>>>>> In order to know if this works I have to recreate the same
> >>>>>>> conditions
> >>>>>>> as on a clean machine without Csound. But I can't seem to do that
> >>>>>>> even when
> >>>>>>> I remove the CsoundLib.framework from Library/Frameworks. Is there
> >>>>>>> anything
> >>>>>>> else I can do to make sure Csound is completely removed from the
> >>>>>>> system? The
> >>>>>>> .app bundle that was causing problems on a fresh machine runs fine
> >>>>>>> on mine?
> >>>>>>> And I haven't ran any of the install_name_tool stuff yet.
> >>>>>>>
> >>>>>>> On 15 October 2015 at 13:54, Rory Walsh  wrote:
> >>>>>>> That's great. Thanks.
> >>>>>>>
> >>>>>>> On 15 October 2015 at 15:43, Victor Lazzarini
> >>>>>>>  wrote:
> >>>>>>> have a look at the build-release.sh script in the installer/macosx/
> >>>>>>> subdirectory.
> >>>>>>>
> >>>>>>> Victor Lazzarini
> >>>>>>> Dean of Arts, Celtic Studies, and Philosophy
> >>>>>>> Maynooth University
> >>>>>>> Ireland
> >>>>>>>
> >>>>>>>> On 15 Oct 2015, at 13:15, Rory Walsh  wrote:
> >>>>>>>>
> >>>>>>>> Yikes. Good to know.
> >>>>>>>>
> >>>>>>>> On 15 October 2015 at 15:03, Victor Lazzarini
> >>>>>>>>  wrote:
> >>>>>>>> yes.
> >>>>>>>>
> >>>>>>>> Victor Lazzarini
> >>>>>>>> Dean of Arts, Celtic Studies, and Philosophy
> >>>>>>>> Maynooth University
> >>>>>>>> Ireland
> >>>>>>>>
> >>>>>>>>> On 15 Oct 2015, at 12:32, Rory Walsh  wrote:
> >>>>>>>>>
> >>>>>>>>> Hmmm. No when I open Cabbage on a machine that doesn't have Csound
> >>>>>>>>> installed it crashes out with an error about libsndfile. Do I have
> >>>>>>>>> to use
> >>>>>>>>> the install_name_tool with every library within the Csound
> >>>>>>>>> framework too?
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 18:20, Rory Walsh  wrote:
> >>>>>>>>> Brilliant. loader_path did the trick :)
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 16:14, Rory Walsh  wrote:
> >>>>>>>>> Thanks Steven. I'll give it a go.
> >>>>>>>>>
> >>>>>>>>> On 13 October 2015 at 16:11, Steven Yi  wrote:
> >>>>>>>>> Maybe try @rpath or @loader_path?  I imagine @executable_path is
> >>>>>>>>> resolving to the VST Host's path.
> >>>>>>>>>
> >>>>>>>>> Check out:
> >>>>>>>>>
> >>>>>>>>> https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath
> >>>>>>>>>
> >>>>>>>>> On Tue, Oct 13, 2015 at 10:52 AM, Rory Walsh 
> >>>>>>>>> wrote:
> >>>>>>>>>> Any Xcode people out who might be able to assist me with this?
> >>>>>>>>>> I'm
> >>>>>>>>>> trying to
> >>>>>>>>>> bundle Csound into my apps by including the framework within the
> >>>>>>>>>> app bundle.
> >>>>>>>>>> To do so I use install_name_tool like this:
> >>>>>>>>>>
> >>>>>>>>>> install_name_tool -id
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>> \
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/sourcecode/csound/build/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>>
> >>>>>>>>>> This works fine for the main Cabbage app bundle, but doesn't
> >>>>>>>>>> work
> >>>>>>>>>> for VST
> >>>>>>>>>> bundles. I don't get it because my VSTs bawk out with the
> >>>>>>>>>> following
> >>>>>>>>>> error:
> >>>>>>>>>>
> >>>>>>>>>> Attempting to load VST:
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst
> >>>>>>>>>> 2015-10-13 15:38:53.132 Plugin Host[24623:1347163] Error loading
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> dlopen(/Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin,
> >>>>>>>>>> 262): Library not loaded:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>>  Referenced from:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /Users/walshr/Library/Audio/Plug-Ins/VST/CabbagePlugin.vst/Contents/MacOS/CabbagePlugin
> >>>>>>>>>>  Reason: image not found
> >>>>>>>>>>
> >>>>>>>>>> But a simple "show package contents" within the .VST bundle
> >>>>>>>>>> shows
> >>>>>>>>>> that the
> >>>>>>>>>> library is located at
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> @executable_path/../Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64
> >>>>>>>>>> as it should be? Any ideas? Xcode drives me nuts.
> >>
> >>
>