Search Unity

Linux command line build of macOS has wrong mono path

Discussion in 'Linux' started by joonturbo, Nov 19, 2021.

  1. joonturbo

    joonturbo

    Joined:
    Jun 24, 2013
    Posts:
    77
    I kept getting the following error on my build machine, running Ubuntu and Unity 2021.2.3f1
    Code (CSharp):
    1.   ##### Output
    2. 15:11:58  System.ArgumentException: Copy() called on path that doesnt exist: /home/ghost/Unity/Hub/Editor/2021.2.3f1/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64ARM64_player_nondevelopment_mono/UnityPlayer.app/Contents/Frameworks/UnityPlayer.dylib
    3. 15:11:58     at NiceIO.NPath.CopyWithDeterminedDestination(NPath destination, Func`2 fileFilter)
    4. 15:11:58     at NiceIO.NPath.Copy(NPath dest, Func`2 fileFilter)
    5. 15:11:58     at NiceIO.NPath.Copy(NPath dest)
    6. 15:11:58     at MacOSCodeSignDylibCopy.Run(CSharpActionContext ctx, SignFlags signFlags)
    7. 15:11:58  [ 90/393    0s] CopyFiles Build/mac/gliderush.app/Contents/Frameworks/libmono-native.dylib
    8. 15:11:58  ##### ExitCode
    I went to look for the path including "macos_x64ARM64_player_nondevelopment_mono"
    and realized it's wrongly capitalized, and should be "macos_x64arm64_player_nondevelopment_mono"

    I was able to fix it, and get proper builds by running
    Code (CSharp):
    1. sudo ln -s /home/myuser/Unity/Hub/Editor/2021.2.3f1/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64arm64_player_nondevelopment_mono  /home/myuser/Unity/Hub/Editor/2021.2.3f1/Editor/Data/PlaybackEngines/MacStandaloneSupport/Variations/macos_x64ARM64_player_nondevelopment_mono
    I am unsure how or where to report a bug for this issue, since I don't ever open the editor on the buildmachine.
    Steps to reproduce:
    - build from command line with target platform as OSXStandalone, on a Linux machine
     
  2. joonturbo

    joonturbo

    Joined:
    Jun 24, 2013
    Posts:
    77
    Just observed that this is still an issue in 2021.2.11
     
  3. PepperPaige

    PepperPaige

    Joined:
    Jan 1, 2018
    Posts:
    1
    Still an issue, although creating a symbolic link worked
     
  4. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    Please submit a bug report
     
  5. Hinuko

    Hinuko

    Joined:
    May 13, 2017
    Posts:
    7
    I submitted a bug report with summary x64arm64/x64ARM64 Case Issue When Building a MacOS Application on Linux on June 3rd. Thank you!
     
    PepperPaige likes this.
  6. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    You will want to post the BugID to be complete, and reference this forum thread in the bug also.
     
  7. Hinuko

    Hinuko

    Joined:
    May 13, 2017
    Posts:
    7
    Hi, I mentioned the link to this forum in my bug report. I'll give you the ID once it is verified and posted on Issue tracker.
     
  8. joonturbo

    joonturbo

    Joined:
    Jun 24, 2013
    Posts:
    77
  9. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    I can confirm the fix is in progress for 2021.3. The pull request is currently under review..
     
    joonturbo likes this.
  10. huulong

    huulong

    Joined:
    Jul 1, 2013
    Posts:
    224
    Fix confirmed on 2021.3.30f1 (so bug was fixed somewhere between 2021.3.7f1 and 2021.3.30f1). I can now build for macOS on Linux without using the symlink hack (and yes I'm sticking to 2021 because it's an old project, but I remember I could build for macOS without issues on 2022.1.24f1 so it was also fixed on 2022).