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: George Warner <email@hidden>
- Date: Thu, 12 Jul 2007 08:58:31 -0700
- Thread-topic: Re[2]: Using a dylib without installing it
Title: Re: Re[2]: Using a dylib without installing it
on 7/11/07 3:00 PM, DAS Loop at <email@hidden> 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.
So far I can solve the bundle problem using the install_name_tool but what about the other application that is not in a bundle? If the user wants to use the GUI-less applications he must to copy somewhere the extra libs ( /usr/lib or /usr/local/lib or /Library/Frameworks/ or ...). But he cannot copy the libraries from the Frameworks bundle in the GUI application as they have been modified with the install_name_tool.
So far the only solution seems to deliver the GUI-less application with another copy of the libraries, this time without any modification and install them in a well know location (what means that I can skip the Frameworks folder in the application bundle :)
Ah! The same applications in Windows are installed in a folder with all the required DLLs. Everything works just fine.
Any good practice on this?
In this case I’d bundle the tool and then link the GUI app against the dylibs in the (bundled) tool since they’re now in a fixed location.
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)
_______________________________________________
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