Dear Christiaan, As I explained earlier, it is easy to use SDKs from older Xcode outside of Xcode itself. Environment variable SDKROOT can be set to point to any SDK, regardless where that SDK folder is kept. With this approach you can use any Xcode you wish and can forget about Apple’s efforts to discourage any developer from supporting older OS X.
E.g. I use currently following collection of SDK’s to maintain backward compatibility from Tiger to Yosemite for RAMSES<http://www.sysecol.ethz.ch/ramses/index>: afischli$ date Sun Oct 11 21:22:07 CEST 2015 afischli$ pwd /Volumes/SED/DeveloperSE/SDKs afischli$ ls -l total 0 drwxr-xr-x 1 afischli staff 264 Mar 1 2015 Applications drwxr-xr-x@ 1 afischli staff 264 Oct 4 2014 MacOSX10.10.sdk drwxrwxr-x 1 afischli staff 264 Mar 1 2015 MacOSX10.4u.sdk drwxrwxr-x 1 afischli staff 264 Mar 1 2015 MacOSX10.5.sdk drwxrwxr-x 1 afischli staff 264 Mar 1 2015 MacOSX10.6.sdk drwxrwxr-x@ 1 afischli staff 264 Mar 1 2015 MacOSX10.7.sdk drwxrwxr-x 1 afischli staff 264 Mar 1 2015 MacOSX10.8.sdk drwxr-xr-x@ 1 afischli staff 264 Aug 27 2014 MacOSX10.9.sdk drwxrwxr-x 1 afischli staff 264 Mar 1 2015 X2.5 I will soon add the SDK for OS X 10.11.x (El Capitan). Whatever Xcode you wish to use in combination with the folder ‘DeveloperSE’ is all I use for backward compatibility. I have even been successfully in constructing pseudo Xcode Applications that let me switch between Xcodes using a command similar to this sudo xcode-select -switch "$newXcodePath” Not sure this helps but wanted to offer these ideas anyway. Regards, Andreas ETH Zurich Prof. em. Dr. Andreas Fischlin Systems Ecology - Institute of Biogeochemistry and Pollutant Dynamics CHN E 21.1 Universitaetstrasse 16 8092 Zurich SWITZERLAND andreas.fisch...@env.ethz.ch<mailto:andreas.fisch...@env.ethz.ch> www.sysecol.ethz.ch<http://www.sysecol.ethz.ch> +41 44 633-6090 phone +41 44 633-1136 fax +41 79 595-4050 mobile Make it as simple as possible, but distrust it! ________________________________________________________________________ On 11 Oct 2015, at 10:40, Christiaan Hofman <cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote: On Oct 11, 2015, at 3:49, Adam R. Maxwell <amaxw...@me.com<mailto:amaxw...@me.com>> wrote: On Oct 10, 2015, at 16:39 , Adam R. Maxwell <amaxw...@me.com<mailto:amaxw...@me.com>> wrote: On Oct 10, 2015, at 15:54 , Christiaan Hofman <cmhof...@gmail.com<mailto:cmhof...@gmail.com>> wrote: Adam, would you know what to do with yaz on 10.11? It seems Apple has removed the open-ssh headers from the 10.11 SDK, and yaw relies on it. I assume you mean openssl? I guess either point yaz at a previous SDK, or (probably Apple's preferred "solution" now) add the openssl source to yaz and bundle it. The worst part of bundling it is supporting multiple OS versions and architectures; that's not easy for autoconf-based projects, which I assume openssl is. Maybe Apple has their version of openssl for Darwin available? More info: http://lists.apple.com/archives/macnetworkprog/2015/Jun/msg00025.html I've actually spent all day dealing with fallout from Apple's stupid Xcode 7 compiler warnings and decision to disallow writing to /usr, which causes problems for MacTeX and TeX Live Utility. -- Adam Unfortunately I have no clue how to do all that, and moreover I have no possibility anymore to test on various versions. Also, I cannot find any SDK anymore except for 10.11 (and I’m on 10.10!) I don’t know what got into Apple lately, but they don’t seem to care about cross development anymore. Do you know how much yaw uses open-ssl, and whether it can work without? Somehow you can build without using it, but I don’t know how that affects the product. Christiaan ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net<mailto:Bibdesk-develop@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
------------------------------------------------------------------------------
_______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
