Hi Carl,
> 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
> On Jan 16, 2016, at 12:21 PM, Scott Ribe wrote:
>
> On Jan 15, 2016, at 11:44 AM, Carl Hoefs
> wrote:
>>
>> Or is the only way to avoid this to use the static archive "*.a" form of the
>> library
>
> FYI, in your example, if
On Jan 16, 2016, at 2:19 AM, Daniel Vollmer 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
On Jan 15, 2016, at 11:44 AM, Carl Hoefs wrote:
>
> Or is the only way to avoid this to use the static archive "*.a" form of the
> library
FYI, in your example, if you add the .a, it (the linker, not Xcode, IIRC) will
use the .dylib instead. The only way to get
Xcode 7.2
Many 3rd party OS X dynamic libraries, (e.g. Mac Ports), get installed with the
following type of soft link arrangement on disk:
lrwxr-xr-x1 root admin15 Aug 28 13:04 libform.dylib ->
libform.6.dylib
-rwxr-xr-x1 root admin 58864 Aug 28 13:04