many development systems enable something called a "link map" but I don't think that's what you want. Michael David Crawford, Consulting Software Engineer [email protected] http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan Area. On Wed, May 20, 2015 at 3:48 AM, Sensei <[email protected]> wrote: > Dear all, > > I have a problem in porting a software to OSX. The problem is not that it > doesn't compile and link, the problem is that I have too many libraries, and > I wish to simplify this situation. > > Adding to a Xcode project 100++ libraries isn't neat but it's how I am > working now: it compiles and links fine. > > So to simplify the project I've tried to create a dummy dylib linking all > legacy libraries, but in linking it doesn't find the needed symbols. It > seems that in linking, legacy libraries do not get pulled in from the dummy > one. > > Once I remember (correct me if I'm wrong) that Xcode had something like a > "link library list file", where I could specify a list of dylib/so files, > but it seems it's gone, or at least, I don't find it. > > Can you suggest me how I can simplify my project? > > Thank you! > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/mdcrawford%40gmail.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
