Re: Non-standard library path with a tool
Re: Non-standard library path with a tool
- Subject: Re: Non-standard library path with a tool
- From: Philip Wasson <email@hidden>
- Date: Thu, 3 May 2007 18:13:44 -0400
On May 3, 2007, at 17:15, George Lawrence Storm wrote:
We build a library as a Framework, Dynamic and Static build.
We then create a series of testrunner (C++) tools to test the
libraries. Our build farm management forbids us from placing our
Frameworks & Dynamic libraries in their normal locations, so I am
copying them to the folder containing my testrunner executable.
When I run my testrunner tool from within the Xcode enviorment the
test runs with no problem, however if I run it as a command line
tool from my ant script it is unable to find the library it is
attempting to test.
Is there a way I can tell my testrunner tool to use the library at
the tools executable root?
You can set environment variables to give the dynamic linker
additional locations in which to search for libraries and frameworks:
DYLD_FRAMEWORK_PATH, DYLD_FALLBACK_FRAMEWORK_PATH, DYLD_LIBRARY_PATH,
and DYLD_FALLBACK_LIBRARY_PATH.
See the man page for dyld.
----------------------------------------------------------------------
Philip D. Wasson pwasson at maned dot com
Software Engineer Managing Editor Inc.
_______________________________________________
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