• 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
Non-standard library path with a tool
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Non-standard library path with a tool


  • Subject: Non-standard library path with a tool
  • From: George Lawrence Storm <email@hidden>
  • Date: Thu, 3 May 2007 14:15:06 -0700

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?

Thanks,

- George Lawrence Storm, DivX, 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


  • Follow-Ups:
    • Re: Non-standard library path with a tool
      • From: Philip Wasson <email@hidden>
  • Prev by Date: Re: Adding more localized *.strings
  • Next by Date: Re: Adding more localized *.strings
  • Previous by thread: Problems building JNI
  • Next by thread: Re: Non-standard library path with a tool
  • Index(es):
    • Date
    • Thread