Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

You need to set the Runpath Search paths in your ScreensaverNinja target to 
@loader_path/../Frameworks not the target Saver which I’m assuming is building 
your framework.

I’m assuming here your ScreenSaver is built from the ScreensaverNinja target 
(the one with the application icon).

Kevin

> On Thu, Jul 2, 2015 at 8:22 PM, Juanjo Conti  > wrote:
> Like this? http://i.imgur.com/4L974ZH.png 
> 
> The problem continues. I'll read the article. Thanks.
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

Ah, the clarification helps.

Does that mean the framework you are loading is none of the targets you are 
listing? and that it is built in a different project?

Then you have set Runpath Search paths to @loader... in the correct target 
(Saver) but you need to remove setting Installation Directory to @rpath.

In the project->target that builds the framework you need to set Installation 
Directory to @rpath and rebuild.

Once doing this your screen saver should work. But your Screen Saver app won’t 
run. You will need to set the Runpath Search paths for the Application to 
@loader_path/../Frameworks as well.

Kevin

> On 3 Jul 2015, at 08:51, Juanjo Conti  wrote:
> 
> I think ScreensaverNinja target does not affect Saver target.
> 
> The Saver target builds a screen saver (a plugin in terms of XCode)
> I'm trying to use the Paddle framework in both, a desktop app 
> (ScreensaverNinja target) and in the screensaver (Saver target).
> 
> In the desktop app works and in the screensaver not.
> 
> Was I clear? Is your reply still valid? What else should I try?
> 
> Thanks,
> 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

Paddle.framework is not one of my targets, it's built by a third party, so
I can't change it. It's this
https://github.com/PaddleHQ/Mac-Framework/archive/master.zip

On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:

> Ah, the clarification helps.
>
> Does that mean the framework you are loading is none of the targets you
> are listing? and that it is built in a different project?
>
> Then you have set Runpath Search paths to @loader... in the correct target
> (Saver) but you need to remove setting Installation Directory to @rpath.
>
> In the project->target that builds the framework you need to set
> Installation Directory to @rpath and rebuild.
>
> Once doing this your screen saver should work. But your Screen Saver app
> won’t run. You will need to set the Runpath Search paths for the
> Application to @loader_path/../Frameworks as well.
>
> Kevin
>
> > On 3 Jul 2015, at 08:51, Juanjo Conti  wrote:
> >
> > I think ScreensaverNinja target does not affect Saver target.
> >
> > The Saver target builds a screen saver (a plugin in terms of XCode)
> > I'm trying to use the Paddle framework in both, a desktop app
> (ScreensaverNinja target) and in the screensaver (Saver target).
> >
> > In the desktop app works and in the screensaver not.
> >
> > Was I clear? Is your reply still valid? What else should I try?
> >
> > Thanks,
> >
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

If I otool -l the binary of the framework, I can read

Load command 3
  cmd LC_ID_DYLIB
  cmdsize 96
 name
@executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle (offset
24)

On Fri, Jul 3, 2015 at 5:27 AM, Juanjo Conti 
wrote:

> Paddle.framework is not one of my targets, it's built by a third party, so
> I can't change it. It's this
> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>
> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>
>> Ah, the clarification helps.
>>
>> Does that mean the framework you are loading is none of the targets you
>> are listing? and that it is built in a different project?
>>
>> Then you have set Runpath Search paths to @loader... in the correct
>> target (Saver) but you need to remove setting Installation Directory to
>> @rpath.
>>
>> In the project->target that builds the framework you need to set
>> Installation Directory to @rpath and rebuild.
>>
>> Once doing this your screen saver should work. But your Screen Saver app
>> won’t run. You will need to set the Runpath Search paths for the
>> Application to @loader_path/../Frameworks as well.
>>
>> Kevin
>>
>> > On 3 Jul 2015, at 08:51, Juanjo Conti  wrote:
>> >
>> > I think ScreensaverNinja target does not affect Saver target.
>> >
>> > The Saver target builds a screen saver (a plugin in terms of XCode)
>> > I'm trying to use the Paddle framework in both, a desktop app
>> (ScreensaverNinja target) and in the screensaver (Saver target).
>> >
>> > In the desktop app works and in the screensaver not.
>> >
>> > Was I clear? Is your reply still valid? What else should I try?
>> >
>> > Thanks,
>> >
>>
>>
>
>
> --
>
> Juanjo Conti http://goog_2023646312>@carouselapps.com
> >
>
> Software Engineer - Carousel Apps 
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

Ah, You might need to talk to the makers of the framework then.

Kevin

> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
> 
> Paddle.framework is not one of my targets, it's built by a third party, so I 
> can't change it. It's this 
> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip 
> 
> 
> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  > wrote:

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

I can do that. What do I ask, to change installation directory to @rpath?
Would that break the other apps using it?

On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:

> Ah, You might need to talk to the makers of the framework then.
>
> Kevin
>
> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
>
> Paddle.framework is not one of my targets, it's built by a third party, so
> I can't change it. It's this
> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>
> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

You are correct making that change would break other apps. I’m not sure what 
the answer is. They might need to build 2 frameworks one with the changed 
installation directory and one without. They might choose to do that for you 
now but in the future, update the installation directory for the framework and 
be clear in release notes that the Runpath Search paths will need to be updated 
in their customers applications.

Kevin

> On 3 Jul 2015, at 09:44, Juanjo Conti  wrote:
> 
> I can do that. What do I ask, to change installation directory to @rpath? 
> Would that break the other apps using it?
> 
> On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  > wrote:
> Ah, You might need to talk to the makers of the framework then.
> 
> Kevin
> 
>> On 3 Jul 2015, at 09:27, Juanjo Conti > > wrote:
>> 
>> Paddle.framework is not one of my targets, it's built by a third party, so I 
>> can't change it. It's this 
>> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip 
>> 
>> 
>> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney > > wrote:
> 
> 
> 
> 
> -- 
> Juanjo Conti http://goog_2023646312/>@carouselapps.com 
> >
> Software Engineer - Carousel Apps 
> 
> 
> Carousel Apps Limited, registered in England & Wales with registered number 
> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
> App Ltd or any of its subsidiary, holding or affiliated companies or entities 
> (together "Watu") is confidential and may be privileged or otherwise 
> protected. If you receive it in error please inform us and then delete it 
> from your system. You should not copy it or disclose its contents to anyone. 
> Messages sent to and from Watu may be monitored to ensure compliance with our 
> internal policies and to protect our business. Emails are not secure and 
> cannot be guaranteed to be error free. Anyone who communicates with us by 
> email is taken to accept these risks.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

There’s two other options

1) Use install_name_tool to change the name in the library to the one you want. 
If it’s shorter, and it should be as the install name in that library seems 
rather long, you can do that

2) Craft the way you package your final product so the library IS in that path 
relative to the executable. 


> On 3 Jul 2015, at 16:44, Juanjo Conti  wrote:
> 
> I can do that. What do I ask, to change installation directory to @rpath?
> Would that break the other apps using it?
> 
> On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
> 
>> Ah, You might need to talk to the makers of the framework then.
>> 
>> Kevin
>> 
>> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
>> 
>> Paddle.framework is not one of my targets, it's built by a third party, so
>> I can't change it. It's this
>> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>> 
>> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>> 
>> 
>> 
> 
> 
> -- 
> 
> Juanjo Conti http://goog_2023646312>@carouselapps.com
> >
> 
> Software Engineer - Carousel Apps 
> 
> -- 
> Carousel Apps Limited, registered in England & Wales with registered number 
> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
> App Ltd or any of its subsidiary, holding or affiliated companies or 
> entities (together "Watu") is confidential and may be privileged or 
> otherwise protected. If you receive it in error please inform us and then 
> delete it from your system. You should not copy it or disclose its contents 
> to anyone. Messages sent to and from Watu may be monitored to ensure 
> compliance with our internal policies and to protect our business. Emails 
> are not secure and cannot be guaranteed to be error free. Anyone who 
> communicates with us by email is taken to accept these risks.
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to r...@rols.org


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[dangerwillrobinsondanger]

This all really needs a DWIM button in Xcode with human friendly descriptions. 

Sent from my iPhone

> On 2015/07/03, at 18:07, Roland King  wrote:
> 
> There’s two other options
> 
> 1) Use install_name_tool to change the name in the library to the one you 
> want. If it’s shorter, and it should be as the install name in that library 
> seems rather long, you can do that
> 
> 2) Craft the way you package your final product so the library IS in that 
> path relative to the executable. 
> 
> 
>> On 3 Jul 2015, at 16:44, Juanjo Conti  wrote:
>> 
>> I can do that. What do I ask, to change installation directory to @rpath?
>> Would that break the other apps using it?
>> 
>>> On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
>>> 
>>> Ah, You might need to talk to the makers of the framework then.
>>> 
>>> Kevin
>>> 
>>> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
>>> 
>>> Paddle.framework is not one of my targets, it's built by a third party, so
>>> I can't change it. It's this
>>> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>>> 
>>> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>> 
>> 
>> -- 
>> 
>> Juanjo Conti http://goog_2023646312>@carouselapps.com
>> >
>> 
>> Software Engineer - Carousel Apps 
>> 
>> -- 
>> Carousel Apps Limited, registered in England & Wales with registered number 
>> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
>> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
>> App Ltd or any of its subsidiary, holding or affiliated companies or 
>> entities (together "Watu") is confidential and may be privileged or 
>> otherwise protected. If you receive it in error please inform us and then 
>> delete it from your system. You should not copy it or disclose its contents 
>> to anyone. Messages sent to and from Watu may be monitored to ensure 
>> compliance with our internal policies and to protect our business. Emails 
>> are not secure and cannot be guaranteed to be error free. Anyone who 
>> communicates with us by email is taken to accept these risks.
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> 
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>> 
>> This email sent to r...@rols.org
> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com
> 
> This email sent to dangerwillrobinsondan...@gmail.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

> On 3 Jul 2015, at 17:12, dangerwillrobinsondan...@gmail.com wrote:
> 
> This all really needs a DWIM button in Xcode with human friendly 
> descriptions. 
> 
> Sent from my iPhone
> 

Perhaps - remember the last time Xcode had a DWIM button however, it was the 
first attempt at AutoLayout and Xcode was very bad at deducing what you meant. 
Rather better now that it’s explicit. 

Similarly for this - it would be handy to have some options on the link with 
library phase to do things like this, assuming the linker actually supports 
doing things like this. 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

From one of the frameworks they replied:


On Fri, Jul 3, 2015 at 5:56 AM, Kevin Meaney  wrote:

> You are correct making that change would break other apps. I’m not sure
> what the answer is. They might need to build 2 frameworks one with the
> changed installation directory and one without. They might choose to do
> that for you now but in the future, update the installation directory for
> the framework and be clear in release notes that the Runpath Search paths
> will need to be updated in their customers applications.
>
> Kevin
>
> On 3 Jul 2015, at 09:44, Juanjo Conti  wrote:
>
> I can do that. What do I ask, to change installation directory to @rpath?
> Would that break the other apps using it?
>
> On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
>
>> Ah, You might need to talk to the makers of the framework then.
>>
>> Kevin
>>
>> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
>>
>> Paddle.framework is not one of my targets, it's built by a third party,
>> so I can't change it. It's this
>> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>>
>> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>>
>>
>>
>
>
> --
> Juanjo Conti http://goog_2023646312/>@carouselapps.com
> >
> Software Engineer - Carousel Apps 
>
>
> Carousel Apps Limited, registered in England & Wales with registered
> number 7689440 and registered office Unit 2 Artbrand Studios, 7
> Leathermarket Street, London SE1 3HN. Any communication sent by or on
> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
> companies or entities (together "Watu") is confidential and may be
> privileged or otherwise protected. If you receive it in error please inform
> us and then delete it from your system. You should not copy it or disclose
> its contents to anyone. Messages sent to and from Watu may be monitored to
> ensure compliance with our internal policies and to protect our business.
> Emails are not secure and cannot be guaranteed to be error free. Anyone who
> communicates with us by email is taken to accept these risks.
>
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

The settings for the Installation Directory is
@executable_path/../Frameworks

On Fri, Jul 3, 2015 at 6:23 AM, Juanjo Conti 
wrote:

> From one of the frameworks they replied:
>
>
> On Fri, Jul 3, 2015 at 5:56 AM, Kevin Meaney  wrote:
>
>> You are correct making that change would break other apps. I’m not sure
>> what the answer is. They might need to build 2 frameworks one with the
>> changed installation directory and one without. They might choose to do
>> that for you now but in the future, update the installation directory for
>> the framework and be clear in release notes that the Runpath Search paths
>> will need to be updated in their customers applications.
>>
>> Kevin
>>
>> On 3 Jul 2015, at 09:44, Juanjo Conti  wrote:
>>
>> I can do that. What do I ask, to change installation directory to @rpath?
>> Would that break the other apps using it?
>>
>> On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
>>
>>> Ah, You might need to talk to the makers of the framework then.
>>>
>>> Kevin
>>>
>>> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
>>>
>>> Paddle.framework is not one of my targets, it's built by a third party,
>>> so I can't change it. It's this
>>> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>>>
>>> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>>>
>>>
>>>
>>
>>
>> --
>> Juanjo Conti http://goog_2023646312/>@carouselapps.com
>> >
>> Software Engineer - Carousel Apps 
>>
>>
>> Carousel Apps Limited, registered in England & Wales with registered
>> number 7689440 and registered office Unit 2 Artbrand Studios, 7
>> Leathermarket Street, London SE1 3HN. Any communication sent by or on
>> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
>> companies or entities (together "Watu") is confidential and may be
>> privileged or otherwise protected. If you receive it in error please inform
>> us and then delete it from your system. You should not copy it or disclose
>> its contents to anyone. Messages sent to and from Watu may be monitored to
>> ensure compliance with our internal policies and to protect our business.
>> Emails are not secure and cannot be guaranteed to be error free. Anyone who
>> communicates with us by email is taken to accept these risks.
>>
>>
>>
>
>
> --
>
> Juanjo Conti http://goog_2023646312>@carouselapps.com
> >
>
> Software Engineer - Carousel Apps 
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

How can I do 1)?

On Fri, Jul 3, 2015 at 6:07 AM, Roland King  wrote:

> There’s two other options
>
> 1) Use install_name_tool to change the name in the library to the one you
> want. If it’s shorter, and it should be as the install name in that library
> seems rather long, you can do that
>
> 2) Craft the way you package your final product so the library IS in that
> path relative to the executable.
>
>
> > On 3 Jul 2015, at 16:44, Juanjo Conti  wrote:
> >
> > I can do that. What do I ask, to change installation directory to @rpath?
> > Would that break the other apps using it?
> >
> > On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
> >
> >> Ah, You might need to talk to the makers of the framework then.
> >>
> >> Kevin
> >>
> >> On 3 Jul 2015, at 09:27, Juanjo Conti  wrote:
> >>
> >> Paddle.framework is not one of my targets, it's built by a third party,
> so
> >> I can't change it. It's this
> >> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
> >>
> >> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
> >>
> >>
> >>
> >
> >
> > --
> >
> > Juanjo Conti http://goog_2023646312>@carouselapps.com
> > >
> >
> > Software Engineer - Carousel Apps 
> >
> > --
> > Carousel Apps Limited, registered in England & Wales with registered
> number
> > 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket
> > Street, London SE1 3HN. Any communication sent by or on behalf of
> Carousel
> > App Ltd or any of its subsidiary, holding or affiliated companies or
> > entities (together "Watu") is confidential and may be privileged or
> > otherwise protected. If you receive it in error please inform us and then
> > delete it from your system. You should not copy it or disclose its
> contents
> > to anyone. Messages sent to and from Watu may be monitored to ensure
> > compliance with our internal policies and to protect our business. Emails
> > are not secure and cannot be guaranteed to be error free. Anyone who
> > communicates with us by email is taken to accept these risks.
> > ___
> >
> > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> >
> > Please do not post admin requests or moderator comments to the list.
> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> >
> > Help/Unsubscribe/Update your Subscription:
> > https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> >
> > This email sent to r...@rols.org
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

Type ‘install_name_tool’ into your favourite search engine and follow in the 
footsteps of the many who went before. 

or type ‘man install_name_tool’ 

but the manual page is a bit terse. 

> On 3 Jul 2015, at 17:25, Juanjo Conti  wrote:
> 
> How can I do 1)?
> 
> On Fri, Jul 3, 2015 at 6:07 AM, Roland King  > wrote:
> There’s two other options
> 
> 1) Use install_name_tool to change the name in the library to the one you 
> want. If it’s shorter, and it should be as the install name in that library 
> seems rather long, you can do that
> 
> 2) Craft the way you package your final product so the library IS in that 
> path relative to the executable.
> 
> 
> > On 3 Jul 2015, at 16:44, Juanjo Conti  > > wrote:
> >
> > I can do that. What do I ask, to change installation directory to @rpath?
> > Would that break the other apps using it?
> >
> > On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  > > wrote:
> >
> >> Ah, You might need to talk to the makers of the framework then.
> >>
> >> Kevin
> >>
> >> On 3 Jul 2015, at 09:27, Juanjo Conti  >> > wrote:
> >>
> >> Paddle.framework is not one of my targets, it's built by a third party, so
> >> I can't change it. It's this
> >> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip 
> >> 
> >>
> >> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  >> > wrote:
> >>
> >>
> >>
> >
> >
> > --
> >
> > Juanjo Conti http://goog_2023646312 
> > >@carouselapps.com 
> > mailto:jjco...@carouselapps.com>>>
> >
> > Software Engineer - Carousel Apps  > >
> >
> > --
> > Carousel Apps Limited, registered in England & Wales with registered number
> > 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket
> > Street, London SE1 3HN. Any communication sent by or on behalf of Carousel
> > App Ltd or any of its subsidiary, holding or affiliated companies or
> > entities (together "Watu") is confidential and may be privileged or
> > otherwise protected. If you receive it in error please inform us and then
> > delete it from your system. You should not copy it or disclose its contents
> > to anyone. Messages sent to and from Watu may be monitored to ensure
> > compliance with our internal policies and to protect our business. Emails
> > are not secure and cannot be guaranteed to be error free. Anyone who
> > communicates with us by email is taken to accept these risks.
> > ___
> >
> > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com 
> > )
> >
> > Please do not post admin requests or moderator comments to the list.
> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com 
> > 
> >
> > Help/Unsubscribe/Update your Subscription:
> > https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org 
> > 
> >
> > This email sent to r...@rols.org 
> 
> 
> 
> 
> -- 
> Juanjo Conti http://goog_2023646312/>@carouselapps.com 
> >
> Software Engineer - Carousel Apps 
> 
> 
> Carousel Apps Limited, registered in England & Wales with registered number 
> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
> App Ltd or any of its subsidiary, holding or affiliated companies or entities 
> (together "Watu") is confidential and may be privileged or otherwise 
> protected. If you receive it in error please inform us and then delete it 
> from your system. You should not copy it or disclose its contents to anyone. 
> Messages sent to and from Watu may be monitored to ensure compliance with our 
> internal policies and to protect our business. Emails are not secure and 
> cannot be guaranteed to be error free. Anyone who communicates with us by 
> email is taken to accept these risks.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

I’m not sure either of those will work.

On 3 Jul 2015, at 10:07, Roland King  wrote:
> 
> There’s two other options
> 
> 1) Use install_name_tool to change the name in the library to the one you 
> want. If it’s shorter, and it should be as the install name in that library 
> seems rather long, you can do that

I don’t think modifying the Installation Directory will work. I’ve checked my 
framework using otool as Juanjo mentioned he did. Building my Framework I’ve 
set Installation Directory to @rpath but the name I see using otool still says 
@executable_path/… etc. so there is some information set elsewhere which 
informs the linker. So I don’t think editing the path using install_name_tool 
will help.

> 2) Craft the way you package your final product so the library IS in that 
> path relative to the executable. 

Except in this case the executable in question will be the screen saver process 
that loads Juanjo’s screensaver plugin.

There is possibly one solution. Modify the name using install_name_tool to 
/Library/Frameworks and install the Framework to /Library/Frameworks.

I still think going to the developers of the framework is the best approach.

Kevin

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

I asked because I've read the man before and I understood it wasn't
possible to change installation dir with it.

On Fri, Jul 3, 2015 at 6:28 AM, Roland King  wrote:

> Type ‘install_name_tool’ into your favourite search engine and follow in
> the footsteps of the many who went before.
>
> or type ‘man install_name_tool’
>
> but the manual page is a bit terse.
>
> On 3 Jul 2015, at 17:25, Juanjo Conti  wrote:
>
> How can I do 1)?
>
> On Fri, Jul 3, 2015 at 6:07 AM, Roland King  wrote:
>
>> There’s two other options
>>
>> 1) Use install_name_tool to change the name in the library to the one you
>> want. If it’s shorter, and it should be as the install name in that library
>> seems rather long, you can do that
>>
>> 2) Craft the way you package your final product so the library IS in that
>> path relative to the executable.
>>
>>
>> > On 3 Jul 2015, at 16:44, Juanjo Conti  wrote:
>> >
>> > I can do that. What do I ask, to change installation directory to
>> @rpath?
>> > Would that break the other apps using it?
>> >
>> > On Fri, Jul 3, 2015 at 5:36 AM, Kevin Meaney  wrote:
>> >
>> >> Ah, You might need to talk to the makers of the framework then.
>> >>
>> >> Kevin
>> >>
>> >> On 3 Jul 2015, at 09:27, Juanjo Conti 
>> wrote:
>> >>
>> >> Paddle.framework is not one of my targets, it's built by a third
>> party, so
>> >> I can't change it. It's this
>> >> https://github.com/PaddleHQ/Mac-Framework/archive/master.zip
>> >>
>> >> On Fri, Jul 3, 2015 at 5:23 AM, Kevin Meaney  wrote:
>> >>
>> >>
>> >>
>> >
>> >
>> > --
>> >
>> > Juanjo Conti http://goog_2023646312>@carouselapps.com
>> > >
>> >
>> > Software Engineer - Carousel Apps 
>> >
>> > --
>> > Carousel Apps Limited, registered in England & Wales with registered
>> number
>> > 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket
>> > Street, London SE1 3HN. Any communication sent by or on behalf of
>> Carousel
>> > App Ltd or any of its subsidiary, holding or affiliated companies or
>> > entities (together "Watu") is confidential and may be privileged or
>> > otherwise protected. If you receive it in error please inform us and
>> then
>> > delete it from your system. You should not copy it or disclose its
>> contents
>> > to anyone. Messages sent to and from Watu may be monitored to ensure
>> > compliance with our internal policies and to protect our business.
>> Emails
>> > are not secure and cannot be guaranteed to be error free. Anyone who
>> > communicates with us by email is taken to accept these risks.
>> > ___
>> >
>> > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> >
>> > Please do not post admin requests or moderator comments to the list.
>> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> >
>> > Help/Unsubscribe/Update your Subscription:
>> > https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>> >
>> > This email sent to r...@rols.org
>>
>>
>
>
> --
> Juanjo Conti http://goog_2023646312/>@carouselapps.com
> >
> Software Engineer - Carousel Apps 
>
>
> Carousel Apps Limited, registered in England & Wales with registered
> number 7689440 and registered office Unit 2 Artbrand Studios, 7
> Leathermarket Street, London SE1 3HN. Any communication sent by or on
> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
> companies or entities (together "Watu") is confidential and may be
> privileged or otherwise protected. If you receive it in error please inform
> us and then delete it from your system. You should not copy it or disclose
> its contents to anyone. Messages sent to and from Watu may be monitored to
> ensure compliance with our internal policies and to protect our business.
> Emails are not secure and cannot be guaranteed to be error free. Anyone who
> communicates with us by email is taken to accept these risks.
>
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

> On 3 Jul 2015, at 17:29, Kevin Meaney  wrote:
> 
> I’m not sure either of those will work.
> 
> On 3 Jul 2015, at 10:07, Roland King mailto:r...@rols.org>> 
> wrote:
>> 
>> There’s two other options
>> 
>> 1) Use install_name_tool to change the name in the library to the one you 
>> want. If it’s shorter, and it should be as the install name in that library 
>> seems rather long, you can do that
> 
> I don’t think modifying the Installation Directory will work. I’ve checked my 
> framework using otool as Juanjo mentioned he did. Building my Framework I’ve 
> set Installation Directory to @rpath but the name I see using otool still 
> says @executable_path/… etc. so there is some information set elsewhere which 
> informs the linker. So I don’t think editing the path using install_name_tool 
> will help.

I think it’ll work just fine, that’s what install_name_tool is there for, 
that’s what I’ve used it for and many others too. You change the install name 
of the thing you’re linking to before you link it and it shows up in a the 
right place in the final executable. 

I believe Mike Ash did a series of two great articles on this. 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

Could you point me to that articles please?

On Fri, Jul 3, 2015 at 6:38 AM, Roland King  wrote:

>
> On 3 Jul 2015, at 17:29, Kevin Meaney  wrote:
>
> I’m not sure either of those will work.
>
> On 3 Jul 2015, at 10:07, Roland King  wrote:
>
>
> There’s two other options
>
> 1) Use install_name_tool to change the name in the library to the one you
> want. If it’s shorter, and it should be as the install name in that library
> seems rather long, you can do that
>
>
> I don’t think modifying the Installation Directory will work. I’ve checked
> my framework using otool as Juanjo mentioned he did. Building my Framework
> I’ve set Installation Directory to @rpath but the name I see using otool
> still says @executable_path/… etc. so there is some information set
> elsewhere which informs the linker. So I don’t think editing the path using
> install_name_tool will help.
>
>
> I think it’ll work just fine, that’s what install_name_tool is there for,
> that’s what I’ve used it for and many others too. You change the install
> name of the thing you’re linking to before you link it and it shows up in a
> the right place in the final executable.
>
> I believe Mike Ash did a series of two great articles on this.
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

www.google.com

"mike ash install_name_tool”


> On 3 Jul 2015, at 17:45, Juanjo Conti  wrote:
> 
> Could you point me to that articles please?
> 
> On Fri, Jul 3, 2015 at 6:38 AM, Roland King  > wrote:
> 
>> On 3 Jul 2015, at 17:29, Kevin Meaney > > wrote:
>> 
>> I’m not sure either of those will work.
>> 
>> On 3 Jul 2015, at 10:07, Roland King mailto:r...@rols.org>> 
>> wrote:
>>> 
>>> There’s two other options
>>> 
>>> 1) Use install_name_tool to change the name in the library to the one you 
>>> want. If it’s shorter, and it should be as the install name in that library 
>>> seems rather long, you can do that
>> 
>> I don’t think modifying the Installation Directory will work. I’ve checked 
>> my framework using otool as Juanjo mentioned he did. Building my Framework 
>> I’ve set Installation Directory to @rpath but the name I see using otool 
>> still says @executable_path/… etc. so there is some information set 
>> elsewhere which informs the linker. So I don’t think editing the path using 
>> install_name_tool will help.
> 
> I think it’ll work just fine, that’s what install_name_tool is there for, 
> that’s what I’ve used it for and many others too. You change the install name 
> of the thing you’re linking to before you link it and it shows up in a the 
> right place in the final executable. 
> 
> I believe Mike Ash did a series of two great articles on this. 
> 
> 
> 
> 
> -- 
> Juanjo Conti http://goog_2023646312/>@carouselapps.com 
> >
> Software Engineer - Carousel Apps 
> 
> 
> Carousel Apps Limited, registered in England & Wales with registered number 
> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
> App Ltd or any of its subsidiary, holding or affiliated companies or entities 
> (together "Watu") is confidential and may be privileged or otherwise 
> protected. If you receive it in error please inform us and then delete it 
> from your system. You should not copy it or disclose its contents to anyone. 
> Messages sent to and from Watu may be monitored to ensure compliance with our 
> internal policies and to protect our business. Emails are not secure and 
> cannot be guaranteed to be error free. Anyone who communicates with us by 
> email is taken to accept these risks.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

I've done that before asking.

On Fri, Jul 3, 2015 at 6:48 AM, Roland King  wrote:

> www.google.com
>
> "mike ash install_name_tool”
>
>
> On 3 Jul 2015, at 17:45, Juanjo Conti  wrote:
>
> Could you point me to that articles please?
>
> On Fri, Jul 3, 2015 at 6:38 AM, Roland King  wrote:
>
>>
>> On 3 Jul 2015, at 17:29, Kevin Meaney  wrote:
>>
>> I’m not sure either of those will work.
>>
>> On 3 Jul 2015, at 10:07, Roland King  wrote:
>>
>>
>> There’s two other options
>>
>> 1) Use install_name_tool to change the name in the library to the one you
>> want. If it’s shorter, and it should be as the install name in that library
>> seems rather long, you can do that
>>
>>
>> I don’t think modifying the Installation Directory will work. I’ve
>> checked my framework using otool as Juanjo mentioned he did. Building my
>> Framework I’ve set Installation Directory to @rpath but the name I see
>> using otool still says @executable_path/… etc. so there is some information
>> set elsewhere which informs the linker. So I don’t think editing the path
>> using install_name_tool will help.
>>
>>
>> I think it’ll work just fine, that’s what install_name_tool is there for,
>> that’s what I’ve used it for and many others too. You change the install
>> name of the thing you’re linking to before you link it and it shows up in a
>> the right place in the final executable.
>>
>> I believe Mike Ash did a series of two great articles on this.
>>
>>
>
>
> --
> Juanjo Conti http://goog_2023646312/>@carouselapps.com
> >
> Software Engineer - Carousel Apps 
>
>
> Carousel Apps Limited, registered in England & Wales with registered
> number 7689440 and registered office Unit 2 Artbrand Studios, 7
> Leathermarket Street, London SE1 3HN. Any communication sent by or on
> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
> companies or entities (together "Watu") is confidential and may be
> privileged or otherwise protected. If you receive it in error please inform
> us and then delete it from your system. You should not copy it or disclose
> its contents to anyone. Messages sent to and from Watu may be monitored to
> ensure compliance with our internal policies and to protect our business.
> Emails are not secure and cannot be guaranteed to be error free. Anyone who
> communicates with us by email is taken to accept these risks.
>
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

First result is the mike ash article I included in my first e-mail to this 
thread.

Kevin

> On 3 Jul 2015, at 10:48, Roland King  wrote:
> 
> www.google.com 
> 
> "mike ash install_name_tool”
> 
> 
>> On 3 Jul 2015, at 17:45, Juanjo Conti  wrote:
>> 
>> Could you point me to that articles please?
>> 
>> On Fri, Jul 3, 2015 at 6:38 AM, Roland King > > wrote:
>> 
>>> On 3 Jul 2015, at 17:29, Kevin Meaney >> > wrote:
>>> 
>>> I’m not sure either of those will work.
>>> 
>>> On 3 Jul 2015, at 10:07, Roland King mailto:r...@rols.org>> 
>>> wrote:
 
 There’s two other options
 
 1) Use install_name_tool to change the name in the library to the one you 
 want. If it’s shorter, and it should be as the install name in that 
 library seems rather long, you can do that
>>> 
>>> I don’t think modifying the Installation Directory will work. I’ve checked 
>>> my framework using otool as Juanjo mentioned he did. Building my Framework 
>>> I’ve set Installation Directory to @rpath but the name I see using otool 
>>> still says @executable_path/… etc. so there is some information set 
>>> elsewhere which informs the linker. So I don’t think editing the path using 
>>> install_name_tool will help.
>> 
>> I think it’ll work just fine, that’s what install_name_tool is there for, 
>> that’s what I’ve used it for and many others too. You change the install 
>> name of the thing you’re linking to before you link it and it shows up in a 
>> the right place in the final executable. 
>> 
>> I believe Mike Ash did a series of two great articles on this. 
>> 
>> 
>> 
>> 
>> -- 
>> Juanjo Conti http://goog_2023646312/>@carouselapps.com 
>> >
>> Software Engineer - Carousel Apps 
>> 
>> 
>> Carousel Apps Limited, registered in England & Wales with registered number 
>> 7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
>> Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
>> App Ltd or any of its subsidiary, holding or affiliated companies or 
>> entities (together "Watu") is confidential and may be privileged or 
>> otherwise protected. If you receive it in error please inform us and then 
>> delete it from your system. You should not copy it or disclose its contents 
>> to anyone. Messages sent to and from Watu may be monitored to ensure 
>> compliance with our internal policies and to protect our business. Emails 
>> are not secure and cannot be guaranteed to be error free. Anyone who 
>> communicates with us by email is taken to accept these risks.
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

Yes, but he doesn't explain install_name_tool there. You said there were 2
articles about install_name_tool.

On Fri, Jul 3, 2015 at 6:56 AM, Kevin Meaney  wrote:

> First result is the mike ash article I included in my first e-mail to this
> thread.
>
> Kevin
>
> On 3 Jul 2015, at 10:48, Roland King  wrote:
>
> www.google.com
>
> "mike ash install_name_tool”
>
>
> On 3 Jul 2015, at 17:45, Juanjo Conti  wrote:
>
> Could you point me to that articles please?
>
> On Fri, Jul 3, 2015 at 6:38 AM, Roland King  wrote:
>
>>
>> On 3 Jul 2015, at 17:29, Kevin Meaney  wrote:
>>
>> I’m not sure either of those will work.
>>
>> On 3 Jul 2015, at 10:07, Roland King  wrote:
>>
>>
>> There’s two other options
>>
>> 1) Use install_name_tool to change the name in the library to the one you
>> want. If it’s shorter, and it should be as the install name in that library
>> seems rather long, you can do that
>>
>>
>> I don’t think modifying the Installation Directory will work. I’ve
>> checked my framework using otool as Juanjo mentioned he did. Building my
>> Framework I’ve set Installation Directory to @rpath but the name I see
>> using otool still says @executable_path/… etc. so there is some information
>> set elsewhere which informs the linker. So I don’t think editing the path
>> using install_name_tool will help.
>>
>>
>> I think it’ll work just fine, that’s what install_name_tool is there for,
>> that’s what I’ve used it for and many others too. You change the install
>> name of the thing you’re linking to before you link it and it shows up in a
>> the right place in the final executable.
>>
>> I believe Mike Ash did a series of two great articles on this.
>>
>>
>
>
> --
> Juanjo Conti http://goog_2023646312/>@carouselapps.com
> >
> Software Engineer - Carousel Apps 
>
>
> Carousel Apps Limited, registered in England & Wales with registered
> number 7689440 and registered office Unit 2 Artbrand Studios, 7
> Leathermarket Street, London SE1 3HN. Any communication sent by or on
> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
> companies or entities (together "Watu") is confidential and may be
> privileged or otherwise protected. If you receive it in error please inform
> us and then delete it from your system. You should not copy it or disclose
> its contents to anyone. Messages sent to and from Watu may be monitored to
> ensure compliance with our internal policies and to protect our business.
> Emails are not secure and cannot be guaranteed to be error free. Anyone who
> communicates with us by email is taken to accept these risks.
>
>
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

Sorry, Roland talked about the 2 articles on install_name_tool.

On Fri, Jul 3, 2015 at 7:26 AM, Juanjo Conti 
wrote:

> Yes, but he doesn't explain install_name_tool there. You said there were
> 2 articles about install_name_tool.
>
> On Fri, Jul 3, 2015 at 6:56 AM, Kevin Meaney  wrote:
>
>> First result is the mike ash article I included in my first e-mail to
>> this thread.
>>
>> Kevin
>>
>> On 3 Jul 2015, at 10:48, Roland King  wrote:
>>
>> www.google.com
>>
>> "mike ash install_name_tool”
>>
>>
>> On 3 Jul 2015, at 17:45, Juanjo Conti  wrote:
>>
>> Could you point me to that articles please?
>>
>> On Fri, Jul 3, 2015 at 6:38 AM, Roland King  wrote:
>>
>>>
>>> On 3 Jul 2015, at 17:29, Kevin Meaney  wrote:
>>>
>>> I’m not sure either of those will work.
>>>
>>> On 3 Jul 2015, at 10:07, Roland King  wrote:
>>>
>>>
>>> There’s two other options
>>>
>>> 1) Use install_name_tool to change the name in the library to the one
>>> you want. If it’s shorter, and it should be as the install name in that
>>> library seems rather long, you can do that
>>>
>>>
>>> I don’t think modifying the Installation Directory will work. I’ve
>>> checked my framework using otool as Juanjo mentioned he did. Building my
>>> Framework I’ve set Installation Directory to @rpath but the name I see
>>> using otool still says @executable_path/… etc. so there is some information
>>> set elsewhere which informs the linker. So I don’t think editing the path
>>> using install_name_tool will help.
>>>
>>>
>>> I think it’ll work just fine, that’s what install_name_tool is there
>>> for, that’s what I’ve used it for and many others too. You change the
>>> install name of the thing you’re linking to before you link it and it shows
>>> up in a the right place in the final executable.
>>>
>>> I believe Mike Ash did a series of two great articles on this.
>>>
>>>
>>
>>
>> --
>> Juanjo Conti http://goog_2023646312/>@carouselapps.com
>> >
>> Software Engineer - Carousel Apps 
>>
>>
>> Carousel Apps Limited, registered in England & Wales with registered
>> number 7689440 and registered office Unit 2 Artbrand Studios, 7
>> Leathermarket Street, London SE1 3HN. Any communication sent by or on
>> behalf of Carousel App Ltd or any of its subsidiary, holding or affiliated
>> companies or entities (together "Watu") is confidential and may be
>> privileged or otherwise protected. If you receive it in error please inform
>> us and then delete it from your system. You should not copy it or disclose
>> its contents to anyone. Messages sent to and from Watu may be monitored to
>> ensure compliance with our internal policies and to protect our business.
>> Emails are not secure and cannot be guaranteed to be error free. Anyone who
>> communicates with us by email is taken to accept these risks.
>>
>>
>>
>>
>
>
> --
>
> Juanjo Conti http://goog_2023646312>@carouselapps.com
> >
>
> Software Engineer - Carousel Apps 
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behalf of Carousel 
App Ltd or any of its subsidiary, holding or affiliated companies or 
entities (together "Watu") is confidential and may be privileged or 
otherwise protected. If you receive it in error please inform us and then 
delete it from your system. You should not copy it or disclose its contents 
to anyone. Messages sent to and from Watu may be monitored to ensure 
compliance with our internal policies and to protect our business. Emails 
are not secure and cannot be guaranteed to be error free. Anyone who 
communicates with us by email is taken to accept these risks.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

 Resending because the last one was > 25K and got held, apologies for the 
dupe which will no-doubt eventually arrive 

Perhaps it was only one - thought it was two - either way I learned most of 
what I knew about how dynamic loading works from that article + a bit of 
reading afterwards. 

So I have finally 15 minutes before Friday’s guests turn up, if I understand 
this rather long thread ..

You have a 3rd party library you’re linking into your app (a screensaver). When 
you link it in the screen save executable can’t find it. It can’t find it 
because the path it’s looking for it, which is buried in the load instructions 
in your binary, is @executable_path/../ but that’s not where 
you’re installing it, which is probably in ../Frameworks or similar. 

So where does the @executable_path/../ come from? That is the install 
name of the library you’re linking in, the 3rd party one. The install name is 
set when you build something and is a promise to the linker that you’re going 
to install the shared library/dynamic library/framework in that place, thats 
why it’s called the install name. So when whoever it was built it, built it, 
they specified @executable_path/../etc and that’s probably where most people 
install it, in the Frameworks directory just under their app in the bundle. 

I don’t know what the executable_path is for a screensaver, you’d think it was 
very much the same thing. So first simplest option is to work out what that is 
and then just put the library at the place it expects to be, 
@executable_path/../Frameworks/. As long as that’s within your 
bundle somewhere, trivial to do. You can even put it somewhere else and put a 
symlink in the bundle. 

If you don’t want to do that or for some reason can’t. The path put into your 
final binary is the ‘install name’ of the library from the library itself. You 
can’t rebuild the library but because this is a REALLY common problem which 
happens all the time, there exists an install_name_tool which lets you change 
it (as long as the new one is shorter than the old one and it helps if the 
developer was nice and padded the original one to leave lots of space). 

I believe the install name of an object can be found by running ‘otool -D 
’, if you do that on the library you’re linking, it  should say 
@executable_path/… 

If you want to change it to something like @rpath/whatever then

install_name_tool -id @rpath/whatever 

You run that on the original 3rd party library, it changes the install name 
compiled in to one of your choosing, and you can have whatever you like and 
then add whatever search paths to your binary you want which will then find it. 
@rpath/ is a good choice because you can always add a search path which will 
find it wherever you put it (and change it for different apps). 

So change the install name in the 3rd party library, re-link your app, the load 
commands should now reflect the install name you just chose. Job done. 

> On 3 Jul 2015, at 18:28, Juanjo Conti  wrote:
> 
> Sorry, Roland talked about the 2 articles on install_name_tool.
> 
> On Fri, Jul 3, 2015 at 7:26 AM, Juanjo Conti  > wrote:
> Yes, but he doesn't explain install_name_tool there. You said there were 2 
> articles about install_name_tool.
> 
> On Fri, Jul 3, 2015 at 6:56 AM, Kevin Meaney  > wrote:
> First result is the mike ash article I included in my first e-mail to this 
> thread.
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Kevin Meaney]

> 
> I don’t know what the executable_path is for a screensaver, you’d think it 
> was very much the same thing. So first simplest option is to work out what 
> that is and then just put the library at the place it expects to be, 
> @executable_path/../Frameworks/. As long as that’s within 
> your bundle somewhere, trivial to do. You can even put it somewhere else and 
> put a symlink in the bundle. 

The @executable_path for the Screen saver will be the path to the executable 
process that loads the OP’s screen saver plugin. in this case ScreenSaverEngine.

> 
> If you want to change it to something like @rpath/whatever then
> 
>   install_name_tool -id @rpath/whatever 

This is where I get confused. In my project not the original posters my 
framework has Installation Directory set to @rpath and everything works as I 
need it to thanks to that Mike Ash article. But if I do otool -D on the 
framework then I see @executable_path … etc. Making me conclude the rpath 
information was stored separately in the binary to the install name so my 
thinking was that modifying the install name wouldn’t help.

Kevin

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

Downloading the zip file referenced earlier and using a simple main.c

$ clang -x c -o main.o -c main.c
$ clang main.o -o main
$ otool -L main
main:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 1213.0.0)

adding the framework right from the unzipped zip and then otool’ing it

$ clang main.o -F ~/Downloads/Mac-Framework-master -framework Paddle -o 
main
$ otool -L main
main:

@executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle 
(compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 1213.0.0)

That’s that @executable_path from the library, using otool -D on it ...

$ otool -D ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle 
/Users/rols/Downloads/Mac-Framework-master/Paddle.framework/Paddle:
@executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle

now update it and check it again

$ install_name_tool -id @rpath/bananas/are/tasty 
~/Downloads/Mac-Framework-master/Paddle.framework/Paddle 

$ otool -D ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle 
/Users/rols/Downloads/Mac-Framework-master/Paddle.framework/Paddle:
@rpath/bananas/are/tasty

and re-link main and then otool it again

$ clang main.o -F ~/Downloads/Mac-Framework-master -framework Paddle -o 
main
$ otool -L main
main:
@rpath/bananas/are/tasty (compatibility version 1.0.0, current 
version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 1213.0.0)

That’s where it comes from - that’s how you can change it. Don’t know what 
you’re seeing. 

> On 3 Jul 2015, at 21:19, Kevin Meaney  wrote:
> 
>> 
>> I don’t know what the executable_path is for a screensaver, you’d think it 
>> was very much the same thing. So first simplest option is to work out what 
>> that is and then just put the library at the place it expects to be, 
>> @executable_path/../Frameworks/. As long as that’s within 
>> your bundle somewhere, trivial to do. You can even put it somewhere else and 
>> put a symlink in the bundle. 
> 
> The @executable_path for the Screen saver will be the path to the executable 
> process that loads the OP’s screen saver plugin. in this case 
> ScreenSaverEngine.
> 
>> 
>> If you want to change it to something like @rpath/whatever then
>> 
>>  install_name_tool -id @rpath/whatever 
> 
> This is where I get confused. In my project not the original posters my 
> framework has Installation Directory set to @rpath and everything works as I 
> need it to thanks to that Mike Ash article. But if I do otool -D on the 
> framework then I see @executable_path … etc. Making me conclude the rpath 
> information was stored separately in the binary to the install name so my 
> thinking was that modifying the install name wouldn’t help.
> 
> Kevin
> 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

Roland, thanks for taking the time for explaining this. I think I'm closer
to the solution but I didn't make it work yet.

The screensaver ends installed in ~/Library/Screen Savers/Ninja.saver/

I was able to cd there and
cd Contents/Frameworks/Paddle.framework/Versions/A, run install_name_tool
command and change the name for the Paddle binary. But I don't know how to
re link it.

So I went to XCode and for the Saver target I added a Run Script phase in
Build Phases, between Copy File (the framework) and Link Binary With
Libraries. The script is:

install_name_tool -id @rpath/
$BUILT_PRODUCTS_DIR/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A/Paddle

After building and installing the screensaver in its destination folder, I
can check with otool that the change was done:

~/Library/Screen
Savers/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A$ otool
-D Paddle

Paddle:

@rpath/

But, when I run the screensaver, I still get the error:

Jul  3 13:30:46 ironbird.local ScreenSaverEngine[74782]: Error loading
/Users/juanjo/Library/Screen Savers/Ninja.saver/Contents/MacOS/Ninja:
 dlopen(/Users/juanjo/Library/Screen
Savers/Ninja.saver/Contents/MacOS/Ninja, 265): Library not loaded:
@executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle

  Referenced from: /Users/juanjo/Library/Screen
Savers/Ninja.saver/Contents/MacOS/Ninja

  Reason: image not found

What can be happening? I think this is related to Kevin doubt.

Thanks in advance for your patient and time.
On Fri, Jul 3, 2015 at 10:57 AM, Roland King  wrote:

> Downloading the zip file referenced earlier and using a simple main.c
>
> $ clang -x c -o main.o -c main.c
> $ clang main.o -o main
> $ otool -L main
> main:
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 1213.0.0)
>
> adding the framework right from the unzipped zip and then otool’ing it
>
> $ clang main.o -F ~/Downloads/Mac-Framework-master -framework
> Paddle -o main
> $ otool -L main
> main:
>
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
> (compatibility version 1.0.0, current version 1.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 1213.0.0)
>
> That’s that @executable_path from the library, using otool -D on it ...
>
> $ otool -D ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
> /Users/rols/Downloads/Mac-Framework-master/Paddle.framework/Paddle:
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
>
> now update it and check it again
>
> $ install_name_tool -id @rpath/bananas/are/tasty
> ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
>
> $ otool -D ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
> /Users/rols/Downloads/Mac-Framework-master/Paddle.framework/Paddle:
> @rpath/bananas/are/tasty
>
> and re-link main and then otool it again
>
> $ clang main.o -F ~/Downloads/Mac-Framework-master -framework
> Paddle -o main
> $ otool -L main
> main:
> @rpath/bananas/are/tasty (compatibility version 1.0.0,
> current version 1.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
> current version 1213.0.0)
>
> That’s where it comes from - that’s how you can change it. Don’t know what
> you’re seeing.
>
> > On 3 Jul 2015, at 21:19, Kevin Meaney  wrote:
> >
> >>
> >> I don’t know what the executable_path is for a screensaver, you’d think
> it was very much the same thing. So first simplest option is to work out
> what that is and then just put the library at the place it expects to be,
> @executable_path/../Frameworks/. As long as that’s within
> your bundle somewhere, trivial to do. You can even put it somewhere else
> and put a symlink in the bundle.
> >
> > The @executable_path for the Screen saver will be the path to the
> executable process that loads the OP’s screen saver plugin. in this case
> ScreenSaverEngine.
> >
> >>
> >> If you want to change it to something like @rpath/whatever then
> >>
> >>  install_name_tool -id @rpath/whatever 
> >
> > This is where I get confused. In my project not the original posters my
> framework has Installation Directory set to @rpath and everything works as
> I need it to thanks to that Mike Ash article. But if I do otool -D on the
> framework then I see @executable_path … etc. Making me conclude the rpath
> information was stored separately in the binary to the install name so my
> thinking was that modifying the install name wouldn’t help.
> >
> > Kevin
> >
>
>


-- 

Juanjo Conti http://goog_2023646312>@carouselapps.com
>

Software Engineer - Carousel Apps 

-- 
Carousel Apps Limited, registered in England & Wales with registered number 
7689440 and registered office Unit 2 Artbrand Studios, 7 Leathermarket 
Street, London SE1 3HN. Any communication sent by or on behal

Re: Problem having a framework working in one of my targets (a screensaver)

[Roland King]

for a start @rpath/ 

won’t work. 

The id name is the actual name of the file, when you substitute the value of 
‘rpath’ in it needs to resolve to an file. So it needs to be @rpath/

You must be install_name_tool’ing the wrong file. The file you’re changing, the 
one in BUILT_PRODUCTS_DIR is not the same one you’re linking with. Think about 
it, that path you are seeing in your final binary, it’s not random, it’s coming 
out of the framework you are linking with, it has to, there is no other place 
it could come from, the linker didn’t just make it up, so if you are changing 
the one in BUILT_PRODUCTS_DIR, and the one in BUILT_PRODUCTS_DIR has the right 
install name and the one in your final binary has the original one, then that 
cannot be the one you’re actually linking with. This string is embedded during 
the link process, so the file the linker finds on the command-line is the one 
it uses, not the one you later copy into the bundle. 

Let me make it really clear. The name embedded in your final binary comes from 
the install name set in the library/framework you link with. There is nowhere 
else it could come from, that is the only information the linker has. So if 
your final binary has @exectuable_path in it, then the framework you are 
actually linking with has that install name set on it. 

Why don’t you copy the original Paddle framework somewhere far far away and 
change the original one in your project to have the correct install name so 
there is nothing in the entire build, nothing on your entire machine, which has 
the original name. 

I picked @rpath/bananas/are/tasty to show quite conclusively that the load name 
is copied verbatim from somewhere in the framework and the place in the 
framework from which it’s copied is the install name (and that 
install_name_tool -id changes that name). If you are still seeing the old path, 
then the library you’re linking with is not the one you’ve changed. 



> On 4 Jul 2015, at 00:32, Juanjo Conti  wrote:
> 
> Roland, thanks for taking the time for explaining this. I think I'm closer to 
> the solution but I didn't make it work yet.
> 
> The screensaver ends installed in ~/Library/Screen Savers/Ninja.saver/
> 
> I was able to cd there and cd 
> Contents/Frameworks/Paddle.framework/Versions/A, run install_name_tool 
> command and change the name for the Paddle binary. But I don't know how to re 
> link it.
> 
> So I went to XCode and for the Saver target I added a Run Script phase in 
> Build Phases, between Copy File (the framework) and Link Binary With 
> Libraries. The script is:
> install_name_tool -id @rpath/ 
> $BUILT_PRODUCTS_DIR/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A/Paddle
> 
> After building and installing the screensaver in its destination folder, I 
> can check with otool that the change was done:
> 
> ~/Library/Screen 
> Savers/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A$ otool -D 
> Paddle
> 
> Paddle:
> 
> 
> @rpath/
> 
> But, when I run the screensaver, I still get the error:
> 
> Jul  3 13:30:46 ironbird.local ScreenSaverEngine[74782]: Error loading 
> /Users/juanjo/Library/Screen Savers/Ninja.saver/Contents/MacOS/Ninja:  
> dlopen(/Users/juanjo/Library/Screen Savers/Ninja.saver/Contents/MacOS/Ninja, 
> 265): Library not loaded: 
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
> 
> Referenced from: /Users/juanjo/Library/Screen 
> Savers/Ninja.saver/Contents/MacOS/Ninja
> 
> Reason: image not found
> 
> What can be happening? I think this is related to Kevin doubt.
> 
> Thanks in advance for your patient and time.
> 
> On Fri, Jul 3, 2015 at 10:57 AM, Roland King  > wrote:
> Downloading the zip file referenced earlier and using a simple main.c
> 
> $ clang -x c -o main.o -c main.c
> $ clang main.o -o main
> $ otool -L main
> main:
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
> current version 1213.0.0)
> 
> adding the framework right from the unzipped zip and then otool’ing it
> 
> $ clang main.o -F ~/Downloads/Mac-Framework-master -framework Paddle 
> -o main
> $ otool -L main
> main:
> 
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle 
> (compatibility version 1.0.0, current version 1.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
> current version 1213.0.0)
> 
> That’s that @executable_path from the library, using otool -D on it ...
> 
> $ otool -D ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
> /Users/rols/Downloads/Mac-Framework-master/Paddle.framework/Paddle:
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
> 
> now update it and check it again
> 
> $ install_name_tool -id @rpath/bananas/are/tasty 
> ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
> 
> $ otool -D ~/Downloads/Mac-Framework-master/Paddle.

Re: Problem having a framework working in one of my targets (a screensaver)

[Juanjo Conti]

I also tried to change the name in the original framework, but that result
in a compilation error <-- and that was because the name was a path instead
of a file. Thanks! Now it's working!

Thanks for the help Roland and Kevin, if you use Mac, we're happy to offer
you a free license of https://screensaver.ninja/

On Fri, Jul 3, 2015 at 2:12 PM, Roland King  wrote:

> for a start @rpath/
>
> won’t work.
>
> The id name is the actual name of the file, when you substitute the value
> of ‘rpath’ in it needs to resolve to an file. So it needs to be
> @rpath/
>
> You must be install_name_tool’ing the wrong file. The file you’re
> changing, the one in BUILT_PRODUCTS_DIR is not the same one you’re linking
> with. Think about it, that path you are seeing in your final binary, it’s
> not random, it’s coming out of the framework you are linking with, it has
> to, there is no other place it could come from, the linker didn’t just make
> it up, so if you are changing the one in BUILT_PRODUCTS_DIR, and the one in
> BUILT_PRODUCTS_DIR has the right install name and the one in your final
> binary has the original one, then that cannot be the one you’re actually
> linking with. This string is embedded during the link process, so the file
> the linker finds on the command-line is the one it uses, not the one you
> later copy into the bundle.
>
> Let me make it really clear. The name embedded in your final binary comes
> from the install name set in the library/framework you link with. There is
> nowhere else it could come from, that is the only information the linker
> has. So if your final binary has @exectuable_path in it, then the framework
> you are actually linking with has that install name set on it.
>
> Why don’t you copy the original Paddle framework somewhere far far away
> and change the original one in your project to have the correct install
> name so there is nothing in the entire build, nothing on your entire
> machine, which has the original name.
>
> I picked @rpath/bananas/are/tasty to show quite conclusively that the load
> name is copied verbatim from somewhere in the framework and the place in
> the framework from which it’s copied is the install name (and that
> install_name_tool -id changes that name). If you are still seeing the old
> path, then the library you’re linking with is not the one you’ve changed.
>
>
>
> On 4 Jul 2015, at 00:32, Juanjo Conti  wrote:
>
> Roland, thanks for taking the time for explaining this. I think I'm closer
> to the solution but I didn't make it work yet.
>
> The screensaver ends installed in ~/Library/Screen Savers/Ninja.saver/
>
> I was able to cd there and
> cd Contents/Frameworks/Paddle.framework/Versions/A, run install_name_tool
> command and change the name for the Paddle binary. But I don't know how to
> re link it.
>
> So I went to XCode and for the Saver target I added a Run Script phase in
> Build Phases, between Copy File (the framework) and Link Binary With
> Libraries. The script is:
>
> install_name_tool -id @rpath/
> $BUILT_PRODUCTS_DIR/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A/Paddle
>
> After building and installing the screensaver in its destination folder, I
> can check with otool that the change was done:
>
> ~/Library/Screen
> Savers/Ninja.saver/Contents/Frameworks/Paddle.framework/Versions/A$ otool
> -D Paddle
>
> Paddle:
>
> @rpath/
>
> But, when I run the screensaver, I still get the error:
>
> Jul  3 13:30:46 ironbird.local ScreenSaverEngine[74782]: Error loading
> /Users/juanjo/Library/Screen Savers/Ninja.saver/Contents/MacOS/Ninja:
>  dlopen(/Users/juanjo/Library/Screen
> Savers/Ninja.saver/Contents/MacOS/Ninja, 265): Library not loaded:
> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
>
>   Referenced from: /Users/juanjo/Library/Screen
> Savers/Ninja.saver/Contents/MacOS/Ninja
>
>   Reason: image not found
>
> What can be happening? I think this is related to Kevin doubt.
>
> Thanks in advance for your patient and time.
> On Fri, Jul 3, 2015 at 10:57 AM, Roland King  wrote:
>
>> Downloading the zip file referenced earlier and using a simple main.c
>>
>> $ clang -x c -o main.o -c main.c
>> $ clang main.o -o main
>> $ otool -L main
>> main:
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
>> current version 1213.0.0)
>>
>> adding the framework right from the unzipped zip and then otool’ing it
>>
>> $ clang main.o -F ~/Downloads/Mac-Framework-master -framework
>> Paddle -o main
>> $ otool -L main
>> main:
>>
>> @executable_path/../Frameworks/Paddle.framework/Versions/A/Paddle
>> (compatibility version 1.0.0, current version 1.0.0)
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
>> current version 1213.0.0)
>>
>> That’s that @executable_path from the library, using otool -D on it ...
>>
>> $ otool -D
>> ~/Downloads/Mac-Framework-master/Paddle.framework/Paddle
>>
>> /Users/rols/Downloads/Mac-Fra