on older systemsįunnily enough, specifying a very low deployment target on Sierra was handled much more gracefully:Į.g.
OSX VERSIONS FULL
Any proposed solution should run on a system that doesn't have the full XCode suite installed. NOTE: my target build hosts are headless CI-machines, that usually will only have the "cmdline" version of the build-tools installed. Ideally something like: CFLAGS+=-mmacosx-version-min=$(shell xcodebuild -minimum-supported-version) So any check should be simple enough to be done at the beginning of the make invocation. My build system is a very simple pure GNU make (no autotools, CMake and the like), and I'd like to keep it that way. So my question is: is there any way to determine programmatically the minimum supported value for -mmacosx-version-min on my build host?
OSX VERSIONS UPDATE
Obviously I could just go and update all my Makefile's to use -mmacosx-version-min=10.6, but I guess I will have the same problem soon enough when Apple decides to ditch 10.6 support. So it seems that recent versions of XCode have a minimum deployment target of OSX-10.6. However, since I've upgraded my build machine to macOS Mojave the builds fail with: This flag is now hardcoded in my Makefile. In the past, I've build my binaries on macOS Sierra using -mmacosx-version-min=10.5, which used to work nicely. To achieve maximum compatibility, I use the -mmacosx-version-min flag when compiling on macOS. The C-programs virtually don't use any libraries apart from libc, and are cross-platform (linux/windows/macOS). The actual number supported versions of OSX/macOS are not so important, but i strive for a maximum coverage ("whatever is possible"). I have a couple of plain C-programs (actually plugins that are dlopen()ed by some host) to compile, and I would like to support as many OSX/macOS versions as possible.
0 kommentar(er)
