Cross-Platform building / packaging kit app, e.g. on linux for target platform windows (or vice versa)

[benedikt.reiser]

We are trying to setup an automated CI/CD pipeline for building and packaging different kit apps for one of our customers. While their users are running Omniverse / kit on Windows, they don’t have dedicated Windows build servers that can be used for CI/CD. So we are evaluating whether it’s possible to build the kit app (fat package) on linux and then run it on Windows.

We’ve been trying with ./repo.sh build -p windows-x86_64 and quickly figured the version lock needs to be regenerated in order to not have windows-specific extensions version-locked as the version lock is platform agnostic right now. However, the build then still fails as it tries to run premake5 while there’s only a premake5.exe.

ERROR    error running: /home/<retracted>/projects/kit-app-template-internal/_build/host-deps/premake/premake5 --file=/home/<retracted>/projects/kit-app-template/premake5.lua gmake2 --platform-host=linux-x86_64               utils.py:264
                             --scripts=/home/<retracted>/.cache/packman/chk/repo_build/0.68.1/lua --platform-target=windows-x86_64 --solution-name=innoactive-kit-app-template --os=linux, code: -1, message: "[Errno 2] No such file or directory:                     
                             '/home/<retracted>/projects/kit-app-template/_build/host-deps/premake/premake5'"  

Trying this on kit 106.0.3 at the moment. Is it even a supported scenario to build and package a kit app on linux for the windows platform or is it a dead end?

[Richard3D]

Yes, this seems like an automatic dead end. You’re just making a lot of work for yourself unnecessarily. If they want to use Windows build the Windows app. If they want to use Linux build a Linux app.
Let’s not make things so much more complicated by trying to make one version of an OS on another version of an OS.

[benedikt.reiser]

Thanks, appreciate the honest answer!