Re: Compiling for 10.9 through 10.12
Re: Compiling for 10.9 through 10.12
- Subject: Re: Compiling for 10.9 through 10.12
- From: Jens Alfke <email@hidden>
- Date: Thu, 21 Jul 2016 10:48:15 -0700
> On Jul 21, 2016, at 9:03 AM, Charles Francoise <email@hidden> wrote:
>
> The problem is that a lot of 3rd-party libraries (libevent, among others) use GNU autotools, which can perform checks for clock_gettime (or getentropy, in another case) and use it if it finds it. A lot of my 3rd-party open-source libraries are breaking retro-compatibility when built with the new SDK because of this.
So the problem has to do with autoconf, which is intended to build a binary *for the computer it’s being run on*. (You’ll run into even worse problems if you try to use an autoconf-built library in an iOS app, for obvious reasons :)
I don’t know much about the details of autoconf, but there may be a way to tell it to use different paths to find headers and libraries (instead of /usr/include and /usr/lib.) If so, you can use that to point it at the SDK you want to build for.
—Jens
_______________________________________________
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