> On Sep 20, 2018, at 3:02 PM, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: > > > >> On Sep 20, 2018, at 2:07 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >> Yes, but based on the above output, the SDK wasn't used. If the SDK had been >> used, a 32-bit build would not have been possible, as far as I understand. >> >
Setting configure.sdkroot to a copy of the MacOSX10.13.sdk does work nicely with Xcode 10 building basiliskii, as expected: configure.sdkroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk /usr/bin/clang++ -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_emulators_basiliskii/basiliskii/work/macemu-1c9b21f580501c5d5833935375945479c5651964/BasiliskII/src/Unix/../include -I/opt/local/include -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -I../MacOSX -I./../include -I./. -I. -I./../CrossPlatform -I./../uae_cpu -I./../slirp -DHAVE_CONFIG_H -DOS_darwin -DDIRECT_ADDRESSING -DUNALIGNED_PROFITABLE -DREGPARAM="__attribute__((regparm(3)))" -DX86_ASSEMBLY -DOPTIMIZED_FLAGS -DSAHF_SETO_PROFITABLE -DUSE_JIT -DUSE_JIT_FPU -DFPU_IEEE -D_REENTRANT -DDATADIR=\"/opt/local/share/BasiliskII\" -pipe -O3 -stdlib=libc++ -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk -arch i386 -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -fomit-frame-pointer -fno-exceptions -fno-merge-constants -fno-gcse-sm -mdynamic-no-pic -c ./../main.cpp -o obj/main.o And the port installs and runs normally. So it appears that on 10.13 with Xcode 10 you can build i386 software with configure.sdkroot “/“ (the default it appears) or configure.sdroot /path/to/MacOSX10.13.sdk Mojave remains to be seen — but I think there is good chance the 10.13 SDK will work there as well to build i386 software (although I’m not sure about the command line tools at “/“). K