> On Sep 18, 2018, at 8:46 AM, Ryan Schmidt <[email protected]> wrote:
> I have not looked into it, but if the macOS SDK in Xcode 10 removes the same > aspects of 32-bit support that macOS Mojave removes, then we may not want to > impose those restrictions on High Sierra, and in that case I would probably > want to keep the High Sierra buildbot on Xcode 9. > I took the leap and installed Xcode 10 on one of my systems running 10.13: macOS 10.13.6 17G65 Xcode 10.0 10A255 and then I built basiliskii freshly from source: sudo port -v -s install basiliskii and watched it build through with -arch i386: /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 -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++ -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 which resulted in an i386 binary at the end: $ file /Applications/MacPorts/BasiliskII/BasiliskII.app/Contents/MacOS/BasiliskII /Applications/MacPorts/BasiliskII/BasiliskII.app/Contents/MacOS/BasiliskII: Mach-O executable i386 Which works correctly when I launch it. So — something is still working right, at least on 10.13 with Xcode 10. Ken
