Re: Re[2]: Using a dylib without installing it
Re: Re[2]: Using a dylib without installing it
- Subject: Re: Re[2]: Using a dylib without installing it
- From: "DAS Loop" <email@hidden>
- Date: Thu, 12 Jul 2007 22:32:28 +0200
Cool :)
Is similar to what software (as Google Earth or Acrobat) does in Linux. They install everything in a location and a script in /usr/local/bin to just call the right application in the right folder setting environment variables before that. Your solution, but, is more elegant.
Thanks for the solution,
David
On 7/12/07, Mike Blaguszewski <email@hidden> wrote:
On Jul 11, 2007, at 6:00 PM, DAS Loop wrote:
Now that we don't have a good solution let me introduce another, related, problem: My product has two versions: a GUI and a GUI-less one. The GUI version is on a bundle, the GUI-less is a non-bundle application that will be on, for example, /usr/local/bin . They share a lot of libraries and frameworks.
Here's how I once solved this problem:
I put the real command line tool inside my GUI's app bundle, so that I could link using @executable_path. Then in /usr/bin I put a stub binary that used the Launch Services API to find a copy of the GUI app. From there it's trivial to construct a path to the bundled command line tool, and you can use the Unix exec() call to run it, forwarding on the arguments in argv.
--
Mike Blaguszewski / Cocoa Hacker / Ambrosia Software, Inc.
--
ALT David in a Loop
_______________________________________________
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