• 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: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets


  • Subject: Re: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
  • From: Grant Erickson <email@hidden>
  • Date: Fri, 24 Jul 2009 15:20:22 -0700
  • Organization: Nuovation System Designs, LLC
  • Thread-topic: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets

On 7/24/09 2:54 PM, Grant Erickson wrote:
> Xcode seems to do a marvelous job at resolving frameworks and their locations
> in the project build results rather than from their normal installed locations
> (i.e. ignoring the path that might show up in otool -D for that framework).
>
> However, I am having more difficulty with external shared libraries (i.e.
> dylibs), in particular, boost.
>
> [ ... snip ... ]
>
> ...I need to tell Xcode "Hey, the libraries you are
> looking for when running the binary are <here>, not in their installed
> locations (e.g. /Library/Application Support/Nuovations/lib) just like the
> five frameworks you resolved."
>
> Toward that end, is there a way to tell Xcode to set LD_LIBRARY_PATH or
> DYLD_LIBRARY_PATH before running a target binary?

Some further trial and error led me to stumble across the 'Executable
"MyApp" Info' pane and the "Variables to be set in the environment:" area.

It would appear that setting either DYLD_FALLBACK_LIBRARY_PATH or
DYLD_LIBRARY_PATH to $(CONFIGURATION_BUILD_DIR)/boost/lib does not work.

However, I can set either DYLD_FALLBACK_LIBRARY_PATH or DYLD_LIBRARY_PATH to
the fully-qualified path and it does work. Unfortunately, this is a
non-starter as someone else who is not me and does not have build results in
my project directory will have to manually change this value.

Again, I suspect Xcode is doing this all under the covers auto-magically for
frameworks, I just need to coax it into doing the right thing for dynamic
libraries.

Regards,

Grant


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets (From: Grant Erickson <email@hidden>)

  • Prev by Date: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
  • Next by Date: Re: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
  • Previous by thread: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
  • Next by thread: Re: Xcode, Dyld, External Dynamic Libraries and Setting {DY}LD_LIBRARY_PATH for Running Targets
  • Index(es):
    • Date
    • Thread