Thanks for the response Chris, For legacy reasons, I need to include OpenSSL and I’ve been using my own build of it for a long while now, without dependency on the OS X included headers. It’s always just worked, until Xcode 7.1. For what it’s worth, when I factor out the OpenSSL dependency, I then get stuck with a similar issue with the leptonica library. So apparently I need to look further than simply an issue with OpenSSL.
Thanks, António > On 12 Nov 2015, at 01:29, Chris Hanson <[email protected]> wrote: > > On Nov 6, 2015, at 9:50 PM, Antonio Nunes <[email protected]> wrote: >> >> Since updating to Xcode 7.1 my project no longer builds because Xcode >> because “bn.h” file not found. I include my own built copy of the openssl >> libraries and header in the project, within a subdirectory of the project >> directory. I made sure that Always search user paths is on, and I have a >> reference to the openssl headers directory in User Header Search Paths. Yet, >> where I try to include bn.h, I get the message “bn.h” file not found. Any >> pointers on how to fix this? > > In general, developers should use CommonCrypto to take the most advantage of > the OS-provided cryptography and security implementations. If there are > things you need to do that can’t be done with CommonCrypto, please file > detailed bugs at <http://bugreport.apple.com/>. > > The OpenSSL headers included in the OS X and iOS SDKs have been deprecated > for a long time, and are now entirely removed from the operating system SDKs. > They have never formally been part of the supported operating system API, > just part of the included Open Source libraries, and the fact that OpenSSL > does not provide a guarantee of release-to-release binary compatibility has > been problematic in the past. > > -- Chris > > _______________________________________________ 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]
