From: Fischlin A. <and...@en...> - 2015-10-26 14:17:57
|
Dear Adam, Yes, this is an engineering problem. What you say is IMHO not accurate, since the main purpose of an SDK is to accomplish exactly this, to be independent of any Xcode and GUIs. Of course, if there should be bugs, something might break with such an approach. But several programmers, not only me, are doing this since years and have never encountered any problem. There was once a bug in one version of the SDK used, Mac OS X 10.4.11 (Tiger), but the bug was present in the Xcode use as well as the SDK used outside of Xcode. BTW, Apple keeps fortunately Xcode and CLTs separate and releases both separately. An SDK is mainly a self-contained CLT - as released by Apple -, but stored within the Xcode app package. But let’s stop arguing. If you don’t like this, forget my hint. I only mentioned it because I believe that this might be helpful for the development of BibDesk, since very convenient and very well working, at least for CLT based development I am very confident. There is basically just one global env var SDKROOT you need to set and you can build for any OS X for which you have an SDK. But I agree, there might be other issues, since I do normally work little with Objective C and my development is largely CLT based only. Cheers, Andreas On 12 Oct 2015, at 16:12, Adam R. Maxwell <ama...@me...<mailto:ama...@me...>> wrote: On Oct 12, 2015, at 01:41 , Fischlin Andreas <and...@en...<mailto:and...@en...>> wrote: So what? I do not think Apple has any rights to control my file system structure and have a say on how I organize my work. A given SDK is tied to the compiler and Xcode with which it was released. Will it work with other versions? Maybe, and if you want to risk that for your personal projects, go for it (but be prepared for it to break in mysterious ways). This is an engineering problem that has nothing to do with your "rights." http://lists.apple.com/archives/xcode-users/2012/Jul/msg00221.html -- adam ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-develop mailing list Bib...@li...<mailto:Bib...@li...> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop |