CI/CD Fails After Adding Cesium for Unity – Partial Method and Reinterop Errors

Cesium for Unity
2

@laserraptor Cesium for Unity has its own CI config in its repo: cesium-unity/.github/workflows/build.yml at main · CesiumGS/cesium-unity · GitHub

It’s important to note that this is the packaging route to building Cesium for Unity - it will produce a build that’s ready to be imported through the Unity Package Manager. If that’s what you’re looking for, the relevant bits are probably:

- name: Build Reinterop
  run: |
    cd d:\cesium\CesiumForUnityBuildProject\Packages\com.cesium.unity
    dotnet publish Reinterop~ -o .

And here:

- name: Build Package
  run: |
    cd d:\cesium\CesiumForUnityBuildProject\Packages\com.cesium.unity
    mkdir -p d:\cesium\temp
    # Store temp files on the D drive, which is much faster than the EBS-backed C drive.
    $ENV:TEMP="d:\cesium\temp"
    # We only need a release build of vcpkg dependencies
    $ENV:CESIUM_VCPKG_RELEASE_ONLY="TRUE"
    # Clear ANDROID_NDK_ROOT so that we use Unity's version
    Remove-Item Env:ANDROID_NDK_ROOT
    # Explicitly set the ezvcpkg path. Otherwise it will be `/.ezvcpkg` and the drive letter is ambiguous.
    $ENV:EZVCPKG_BASEDIR="D:/.ezvcpkg"
    # Run the build
    dotnet run --project Build~

If you’re looking instead to make an “in-place” build, you should take a look at the Developer Setup guide which gives instructions for setting up and building Cesium for Unity from source.