amzn-changml
commented
1 year ago This seems cross cutting with sig-build and sig-platform. Could you provide some more details about the issues you've found? I'll try to repro, but we should issue bugs for anything missing in the monolithic builds.
tonybalandiuk
Describe the issue
This issue was discovered related to release for 23.05 SDK. When trying to follow the instructions for creating a project game release layout, it seems that the SDK path does not yield expected behavior (see the link provided in Impacted Pages). There were various issues with cmake not finding the right binary executables, and monolithic build artifacts.
Current consensus with engineers seems to be that certain artifacts have to be built first using the source build of the engine, migrate it to the SDK installation, then proceed with the rest of the packaging process.
Currently I see that there are some efforts to debug and fix the SDK release, so a deeper review of the system may be needed to update the documentation accurately. Alternate instructions will need to be provided at some point. In the meantime, it's recommended to temporarily mark that route as unavailable for project release.
Impacted page(s)
https://www.o3de.org/docs/user-guide/packaging/windows-release-builds/#create-a-project-game-release-layout
Expected experience
I expected that, with a relatively simple project (the empty test project with just a shader ball scene), following either path of instructions would yield correct results. Currently it seems that I don't see issues with source built path, but with SDK path, I'm unable to complete the instructions due to lack of necessary executable binaries and monolithic artifacts to build the game properly.