My very-first-ever XCode test for kha/iOS doesn't build (see below).
(Maybe not actually a kha problem, rather a XCode-target-related one?)

I'm on
High Sierra 10.13.6
XCode 10.1 beta 3
Any ideas?

/ Jonas

Lexical or Preprocessor Issue Group
/Users/Hanna/Desktop/Jonas/Kha/Kha/Kinc/Backends/System/iOS/Sources/Kore/GLView.h:5:9: 'QuartzCore/CAMetalLayer.h' file not found
/Users/Hanna/Desktop/Jonas/Kha/Kha/Kinc/Backends/System/iOS/Sources/Kore/KoreAppDelegate.mm:3:9: In file included from /Users/Hanna/Desktop/Jonas/Kha/Kha/Kinc/Backends/System/iOS/Sources/Kore/KoreAppDelegate.mm:3:

Are you compiling for the simulator? Because that one only supports Metal in macOS 10.15.

Yep, not tried real hardware yet.

So, compiling on osx 10.13 using XCode version for that system targeting iPhone simulator needs osx 10.15 to build..?
How could that even be theoretically possible..!? Apple black magic i guess...

Will try hardware asap.

Metal in the simulator needs macOS 10.15, as I said. You can use the -g opengl switch but I would generally advice against using the simulator anyway. Just using Kha's macOS target gets you as close to how things work on iOS as the simulator does - if not more so.

Thanks!

One step closer:
osx-build: Building and running for Mac desktop works fine
ios-build: Building for physical iPad 2018 9'7 device now works fine until the linking step. Seems related to Kore::System::showsKeyboard() from what I can tell from the log output below.

Ideas?

/clang:-1: linker command failed with exit code 1 (use -v to see invocation)

Undefined symbols for architecture arm64:
  "_kinc_keyboard_active", referenced from:
      Kore::System::showsKeyboard() in System-997655bb3c51406d12fe3f3812c44f301d4f75e58cf1c440342676fd3f9ccf2f.o
ld: symbol(s) not found for architecture arm64

Ld /Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Products/Debug-iphoneos/New\ Project.app/New\ Project normal arm64 (in target: New Project)
    cd /Users/Hanna/Desktop/Jonas/testKhaIos2/Build/ios-build
    export IPHONEOS_DEPLOYMENT_TARGET=8.0
    /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch arm64 -isysroot /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.1.sdk -L/Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Products/Debug-iphoneos -F/Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Products/Debug-iphoneos -filelist /Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Intermediates.noindex/New-Project.build/Debug-iphoneos/New\ Project.build/Objects-normal/arm64/New\ Project.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -miphoneos-version-min=8.0 -dead_strip -Xlinker -object_path_lto -Xlinker /Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Intermediates.noindex/New-Project.build/Debug-iphoneos/New\ Project.build/Objects-normal/arm64/New\ Project_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fembed-bitcode-marker -fobjc-arc -fobjc-link-runtime -framework Metal -framework UIKit -framework Foundation -framework CoreGraphics -framework QuartzCore -framework CoreAudio -framework AudioToolbox -framework CoreMotion -framework AVFoundation -framework CoreFoundation -framework CoreVideo -framework CoreMedia -Xlinker -dependency_info -Xlinker /Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Intermediates.noindex/New-Project.build/Debug-iphoneos/New\ Project.build/Objects-normal/arm64/New\ Project_dependency_info.dat -o /Users/Hanna/Library/Developer/Xcode/DerivedData/New-Project-elwvojzbzeatqbaoiwxkgvczxpee/Build/Products/Debug-iphoneos/New\ Project.app/New\ Project

Should be fixed now.

Thank you, Rob!
So, finally it builds and ... runs... almost!

Bloody hell, Apple, get your shit together..!

Hihi. Ya, upwards and downwards compatibility doesn't have high priority in Cupertino.

Wrong. It has high priority, in the sense of "How-much-can-we-earn-on-causing-troubles-with-compatibility-issues..?"