• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Prebinding problems with shared framework
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Prebinding problems with shared framework


  • Subject: Re: Prebinding problems with shared framework
  • From: Jim Ingham <email@hidden>
  • Date: Wed, 24 Mar 2004 11:26:41 -0800

Dario,


On Mar 24, 2004, at 11:14 AM, Dario Accornero wrote:


On 24 Mar 2004, at 20:06, Jim Ingham wrote:

Yes, that's right. You don't have an installer package, so you can't use the -pkgs option. The reason for suggesting this is to see if the problem is in the prebinding itself, or just in the fix_prebinding tool...

From /Library/Frameworks, I've used the following command

update_prebinding -root / -files OpenAL.framework/Versions/A/OpenAL

which apparently completed successfully

2004-03-24 20:09:58.129 update_prebinding[7004] Prebinding files (0/1 complete)
2004-03-24 20:09:58.209 update_prebinding[7004] update_prebinding done. (100/100 complete)
2004-03-24 20:09:58.210 update_prebinding[7004] Update_prebinding done.
2004-03-24 20:09:58.210 update_prebinding[7004] 1 files successfully prebound, 0 files unsuccessfully prebound.


After having relinked the application, it looks like the message has disappeared. Still, I don't understand why the error was referring to a framework inside my bundle, whereas the framework is in /Library ...


No idea, I don't work on fix_prebinding. Maybe this is just the last element in the list of locations that it tries looking for the library??? Dunno...


Thanks a lot,
Dario

Jim


On Mar 24, 2004, at 10:54 AM, Dario Accornero wrote:

On 24 Mar 2004, at 19:42, Jim Ingham wrote:

Is your framework on a volume other than the root volume? I think that fix_prebinding doesn't fix files on other volumes because it doesn't want to get into the situation where two users with different system versions are mounting the same volume, and then fighting with each other about the correct prebinding of the file...

No, everything is on the same (the only) volume.

Also, did you try directly running update_prebinding on the framework?

Should I use the -files option? I've never used it before...

Thanks,
Dario

Jim

On Mar 24, 2004, at 2:25 AM, Dario Accornero wrote:

Anybody? I'd be happy to be told to just RTFM, only the FM says that this situation should not happen...

Thanks,
Dario

On 23 Mar 2004, at 13:51, I wrote:

I am using the OpenAL framework, which has installed itself in /Library/Frameworks, and linking against it in my Carbon application. It is a standard framework with plain C interfaces. Xcode 1.1 does not give me any error messages when I build my application on 7F44, but whenever I try to launch it I find the classic message in the console:

Mar 23 13:43:10 localhost /usr/libexec/fix_prebinding: /path/to/my/application.app/Contents/MacOS/application could not be launched prebound.
Mar 23 13:43:10 localhost /usr/libexec/fix_prebinding: update_prebinding (finding dependent libraries for /path/to/my/application.app/Contents/Frameworks/OpenAL.framework/ Versions/A/OpenAL): can't open file: /path/to/my/application.app/Contents/Frameworks/OpenAL.framework/ Versions/A/OpenAL (No such file or directory)
Mar 23 13:43:10 localhost /usr/libexec/fix_prebinding: The file /path/to/my/application.app/Contents/Frameworks/OpenAL.framework/ Versions/A/OpenAL does not exist
Mar 23 13:43:10 localhost /usr/libexec/fix_prebinding: As a result, fix_prebinding will not attempt to prebind the application.
Mar 23 13:43:10 localhost /usr/libexec/fix_prebinding: 2004-03-23 13:43:10 +0100: prebinding for application done.
Mar 23 13:45:10 localhost /usr/libexec/fix_prebinding: fix_prebinding quitting for now.


I am *not* using the "@executable/.../Frameworks" path in my project -- I have just added the framework to the project, and since it compiled and linked fine the very first time (and it still does), I did not suspect any problems.

How can I get rid of the above error in this situation?
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.



--
Jim Ingham                                   email@hidden
Developer Tools
Apple Computer



--
Jim Ingham                                   email@hidden
Developer Tools
Apple Computer



--
Jim Ingham                                   email@hidden
Developer Tools
Apple Computer
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


References: 
 >Prebinding problems with shared framework (From: Dario Accornero <email@hidden>)
 >Re: Prebinding problems with shared framework (From: Dario Accornero <email@hidden>)
 >Re: Prebinding problems with shared framework (From: Jim Ingham <email@hidden>)
 >Re: Prebinding problems with shared framework (From: Dario Accornero <email@hidden>)
 >Re: Prebinding problems with shared framework (From: Jim Ingham <email@hidden>)
 >Re: Prebinding problems with shared framework (From: Dario Accornero <email@hidden>)

  • Prev by Date: Re: Prebinding problems with shared framework
  • Next by Date: Re: Library style 'static' ignored for frameworks?
  • Previous by thread: Re: Prebinding problems with shared framework
  • Next by thread: Re: Prebinding problems with shared framework
  • Index(es):
    • Date
    • Thread