On Jan 16, 2016, at 2:19 AM, Daniel Vollmer <[email protected]> wrote: > >> When adding dynamic libraries to my OS X project (using the Target -> Build >> Phases -> Link Binary With Libraries window), Xcode resolves “libform.dylib" >> to the specific version, "libform.6.dylib", and adds that string instead to >> the build phase. > >> Is there a way I can have Xcode simply retain the "libXXXX.dylib" string >> without resolving it until build time? Or is the only way to avoid this to >> use the static archive "*.a" form of the library, which doesn't include the >> version number, but loses the benefits of using dynamic libraries? > > I had the same problem, and what I did was to edit the Xcode-project file in > a text editor (with Xcode closed) and changed all references to the link > target by the name of the link itself (e.g. change libXXXX.6.dylib back to > libXXX.dylib). It seems Xcode only does the lookup once when adding a new > file and not every time it used (or more likely the File Open dialogue does > it). > Thanks for the suggestion, Daniel. I guess I have no other option. Sure beats dropping and re-adding a dozen or so libraries on every active project every time I switch machines (or every time someone updates Mac ports). By tying a project to specific library versions, this "feature" of Xcode removes one of the benefits of using dynamic libraries.
-Carl _______________________________________________ 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]
