It's possible to build a Unity project either by exporting symbols to an archive, which is supported, or by using Unity's internal Gradle build. This changeset adds support for uploading Unity SO mapping files for the second use case.
Changeset
Searched the Temp/StagingArea/symbols directory for libunity/libil2cpp SO files
Generated SO mapping files using the symbols in the Temp/StagingArea/symbols directory
Testing
Manually tested on a Unity 2018 and 2019 example project and confirmed that a SO mapping file was generated in the appropriate build directory. Due to the nature of the change E2E tests were not seen as feasible on CI for now and manual testing was agreed as part of the design.
Goal
It's possible to build a Unity project either by exporting symbols to an archive, which is supported, or by using Unity's internal Gradle build. This changeset adds support for uploading Unity SO mapping files for the second use case.
Changeset
Temp/StagingArea/symbolsdirectory forlibunity/libil2cppSO filesTemp/StagingArea/symbolsdirectoryTesting
Manually tested on a Unity 2018 and 2019 example project and confirmed that a SO mapping file was generated in the appropriate build directory. Due to the nature of the change E2E tests were not seen as feasible on CI for now and manual testing was agreed as part of the design.