Re: Adding a symlink (not its target) to a project (libz.dylib post security update)
Re: Adding a symlink (not its target) to a project (libz.dylib post security update)
- Subject: Re: Adding a symlink (not its target) to a project (libz.dylib post security update)
- From: "Sean McBride" <email@hidden>
- Date: Thu, 18 Aug 2005 13:21:04 -0400
- Organization: Rogue Research
On 2005-08-17 09:24, Sean McBride said:
>My project requires functions from libz.dylib, so I added it to the
>project. All was well. At the time I never noticed but it resolved the
>symlink and actually added libz.1.2.2.dylib to the project. The latest
>security update removed that file and added libz.1.2.3.dylib. Now my
>project won't build.
OK, so now I know that I have to add it to the project by drag and drop,
due to that NSOpenPanel bug. But there are new problems.... :)
1) If I look at the build log I see that the symlink seems to be getting
resolved anyway:
/usr/bin/g++-4.0 <SNIP!> -lz.1.2.3 <SNIP!>
Does this mean my app won't work on pre-Security Update 2005-007 systems?
2) If I switch to the 10.4u SDK (as opposed to 'current Mac OS'),
linking fails since the 10.4u SDK has 1.2.2 not 1.2.3.
What is the right way to link against this library? I need my app to
run on 10.2.8 and later, and use whatever version of libz they have on
their system.
Thanks!
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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