Cesium for Unity on Apple Vision Pro - Xcode Build Errors

TheoACN · May 13, 2024, 9:29pm

I am attempting to integrate the Cesium for Unity package into the Unity PolySpatial template project and build to Apple Vision Pro. I’ve encountered multiple build errors throughout the process and have used suggestions on this board to make it a bit further, but I still haven’t managed to successfully build in Xcode yet. I’m using Unity 2022.3.19f1.

Initially Unity would show errors pertaining to the “Reinterop” class or namespace. A workaround suggested in this thread is to add the package locally rather than via scoped registry so that I can manually add UNITY_VISIONOS to all #IF UNITY_IOS preprocessor conditions. I also had to disable Burst compiling and optimizations in the Burst AOT Settings & check VisionOS on the iOS plugin libraries. This does result in an Xcode project, but attempting to build in Xcode presents its own errors, this time with undefined symbols. The majority of the errors seem to be with Cesium types or namespaces like CesiumGltf, CesiumUtility, Cesium3DTilesContent and similar, however there are also undefined symbols scoped under Fmt::v8::detail, Async::detail, and Spdlog. Here’s a gist with all the undefined symbol errors: CesiumForUnityVisionOSXcodeErrors.txt · GitHub

Has anyone else run into this issue when attempting to build to Apple Vision Pro? I know at least one other person has done it based on this thread but they didn’t mention any build issues. Also is official Vision Pro support planned for the plugin? Thanks in advance!

Kevin_Ring · May 14, 2024, 1:24am

I can’t give you complete instructions, because I don’t have a Vision Pro and have never tried to build for it. However, one thing that is certain is that building for a new platform from the release package will not work. You need to clone the cesium-unity repo and build it from source. The basic process for doing so is described here, but it really only covers Windows:

github.com

CesiumGS/cesium-unity/blob/main/Documentation~/developer-setup.md

# Overview

This is a summary of the setup and workflows for developers who want to modify the Cesium for Unity plugin. If you just want to use Cesium for Unity in your own applications, see the main [README](../README.md).

## :computer: Building Cesium for Unity

### Prerequisites

* CMake v3.18 or later (the latest version is recommended)
* [.NET SDK v6.0 or later](https://dotnet.microsoft.com/en-us/download/dotnet/6.0)
* If you're using Visual Studio, you need Visual Studio 2022.
* Unity 2021.3+ (the latest version of the Unity 2021.3 LTS release is recommended)
* On Windows, support for long file paths must be enabled, or you are likely to see build errors. See [Maximum Path Length Limitation](https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later).
* For best JPEG-decoding performance, you must have [nasm](https://www.nasm.us/) installed so that CMake can find it. Everything will work fine without it, just slower.

The built Cesium for Unity Assembly will run on much older versions of .NET, including the version of Mono included in Unity. However, these very recent versions are required for the C#<->C++ interop code generator (Reinterop).

To make sure things are set up correctly, open a command-prompt (PowerShell is a good choice on Windows) and run:

* `dotnet --version` and verify that it reports 6.0 or later

This file has been truncated. show original

Another useful resource is our GitHub Actions workflow, which shows how Cesium for Unity is built by our CI system for macOS and iOS:

github.com

CesiumGS/cesium-unity/blob/6e82d93812c739470ff60775c6067d4f8b0c9251/.github/workflows/build.yml#L107


      
                run: |
                  start -FilePath "C:\Program Files\Unity\Hub\Editor\2021.3.13f1\Editor\Unity.exe" -ArgumentList "-runTests -batchmode -projectPath d:\cesium\CesiumForUnityBuildProject -testResults d:\cesium\temp\TestResults.xml -testPlatform PlayMode -logFile d:\cesium\temp\test-log.txt" -Wait
                  cat d:\cesium\temp\test-log.txt
              - name: Test Report
                uses: kring/test-reporter@v1.6.2-kring
                if: success() || failure()    # run this step even if previous step failed
                with:
                  name: Tests - Windows
                  path: d:/cesium/temp/TestResults.xml
                  reporter: dotnet-nunit
          MacOS:
            needs: [QuickChecks]
            runs-on: macos-12
            # Only allow a single macOS build at a time, for Unity licensing reasons
            concurrency: mac
            steps:
              - name: Set XCode version
                uses: maxim-lobanov/setup-xcode@v1
                with:
                  xcode-version: "14.1"
              - name: Check out repository code

A key part of that script is dotnet run --project Build~, which invokes this script:

github.com

CesiumGS/cesium-unity/blob/main/Build~/Package.cs

using System;
using System.Diagnostics;
using System.IO;
using System.Text;
using System.Collections.Generic;
using System.Linq;

namespace Build
{
    public class Package
    {
        public void Run()
        {
            Unity? unity = Unity.FindUnity();
            if (unity == null)
                throw new Exception("Could not find Unity!");
            Cmake cmake = new Cmake();

            Console.WriteLine("**** Using Unity at " + unity.ExecutablePath);

This file has been truncated. show original

And that script, in turn, runs Unity from the command-line several times in order to build the project, which ends up running functions from here inside Unity:

github.com

CesiumGS/cesium-unity/blob/main/Editor/BuildCesiumForUnity.cs

using System;
using System.IO;
using System.Linq;
using System.Runtime.CompilerServices;
using System.Text;
using System.Threading;
using UnityEditor;
using UnityEditor.Build.Reporting;
using UnityEditor.Compilation;
using UnityEditor.PackageManager;
using UnityEditor.PackageManager.Requests;
using UnityEngine;

namespace CesiumForUnity
{
    public class BuildCesiumForUnity
    {
        public static void CompileForEditorAndExit()
        {
            CompilationPipeline.compilationFinished += OnEditorCompilationFinished;

This file has been truncated. show original

And, via Unity magic, parts of this are invoked during that process in order to build the native code:

github.com

CesiumGS/cesium-unity/blob/main/Editor/CompileCesiumForUnityNative.cs

using UnityEditor;
using UnityEngine;
using UnityEditor.Build;
using UnityEditor.Build.Reporting;
using System.Diagnostics;
using System.Runtime.CompilerServices;
using System.IO;
using System.Text;
using System;
using System.Collections.Generic;
#if UNITY_ANDROID
using UnityEditor.Android;
#endif

namespace CesiumForUnity
{
    internal struct PlatformToBuild
    {
        public BuildTargetGroup platformGroup;
        public BuildTarget platform;

This file has been truncated. show original

Topic		Replies	Views
Cesium Unity on Apple Vision Pro Cesium for Unity	7	755	September 13, 2024
XCode Runtime and Build errors when building for VisionOS Cesium for Unity	0	26	September 20, 2024
Cesium support for unity Vision Pro Cesium for Unity	1	420	March 29, 2024
Xcode errors when building after installing Cesium Cesium for Unity	2	286	June 6, 2023
Xcode building error Cesium for Unity	9	260	September 20, 2023

Cesium for Unity on Apple Vision Pro - Xcode Build Errors

Related Topics