Search Unity

Xcode 11 (macOS SDK 10.15) timeframe?

Discussion in 'macOS' started by HiddenJason, Sep 25, 2019.

  1. HiddenJason

    HiddenJason

    Joined:
    Apr 18, 2016
    Posts:
    23
    Apple just pushed out the official release of Xcode 11. That removes the older macOS SDKs and only includes macOS SDK 10.15. The current version of il2cpp included in Unity only handles up to macOS SDK 10.14.

    What's the expected timeframe for an update, given that this prevents building for macOS?

     
    HiddenJason, Sep 25, 2019
    #1

  2. HiddenJason

    HiddenJason

    Joined:
    Apr 18, 2016
    Posts:
    23
    Just to verify: this still occurs with 2018.4.10f1.

     
    HiddenJason, Oct 2, 2019
    #2

  3. lasercannon

    lasercannon

    Joined:
    Nov 29, 2012
    Posts:
    80
    Hi @HiddenJason, we're having the same issue here. Do you have a workaround?
     
    lasercannon, Oct 3, 2019
    #3

  4. HiddenJason

    HiddenJason

    Joined:
    Apr 18, 2016
    Posts:
    23
    None yet. We're hoping for a reasonably quick turnaround from Unity instead of spending time finding our own fix since this will be affecting more and more Mac users as they update to Xcode 11.
     
    HiddenJason, Oct 3, 2019
    #4

  5. lasercannon

    lasercannon

    Joined:
    Nov 29, 2012
    Posts:
    80
    I ended up finding a fix! If you navigate to that path, duplicate the 10.15 symlink and rename it "10.14", everything seems to work as expected.
     
    lasercannon, Oct 4, 2019
    #5
    NonPlayerCorey and HiddenJason like this.

  6. HiddenJason

    HiddenJason

    Joined:
    Apr 18, 2016
    Posts:
    23
    That's pretty close to the workaround I came up with: install Xcode 10.3 as a manual install (downloaded from Apple Developer website), and then symlink from the Xcode 11 app bundle SDKs folder to MacOSX10.14.sdk in the Xcode 10.3 app bundle.
     
    HiddenJason, Oct 5, 2019
    #6

  7. andrews_unity

    andrews_unity

    Unity Technologies

    Joined:
    Dec 11, 2015
    Posts:
    264
    So for 2018.4 this should be resolved in the next update, this is not an issue in 2019. Essentially it will use whatever xcode has selected as the default SDK instead of the hardcoded list.
     
    andrews_unity, Oct 10, 2019
    #7

  8. Deleted User

    Deleted User

    Guest

    I am having the same issue, using Unity version 2018.2 - and I don't want to upgrade if I can get this issue solved since I am doing an update of my existing game on Steam.
    So could You please be so kind to elaborate on how You do this, I understand I have to use the terminal but not much more?
     
    Deleted User, Oct 15, 2019
    #8

  9. turdann

    turdann

    Joined:
    Dec 29, 2012
    Posts:
    43
    What about 2017.4? There's no backporting?
     
    turdann, Oct 16, 2019
    #9

  10. CliffCawley

    CliffCawley

    Joined:
    Mar 30, 2009
    Posts:
    22
    This is still an issue in 2018.4.11
     
    CliffCawley, Oct 17, 2019
    #10

  11. bitinn

    bitinn

    Joined:
    Aug 20, 2016
    Posts:
    961
    Until the next version is released, confirm the symbolic link workaround does work.

    All you need to do is:

    Code (CSharp):
    1. cd /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
    2. sudo ln -s MacOSX.sdk MacOSX10.14.sdk
    il2cpp build should work after that.
     
    bitinn, Oct 28, 2019
    #11

  12. HiddenJason

    HiddenJason

    Joined:
    Apr 18, 2016
    Posts:
    23
    It turns out that works until macOS decides to automatically "fix" the installation and delete the symlink.
     
    HiddenJason, Nov 1, 2019
    #12

  13. bitinn

    bitinn

    Joined:
    Aug 20, 2016
    Posts:
    961
    The fixed version is already out, so download that instead :)
     
    bitinn, Nov 1, 2019
    #13

  14. NonPlayerCorey

    NonPlayerCorey

    Joined:
    Aug 13, 2015
    Posts:
    14
    NonPlayerCorey, Dec 13, 2019
    #14