-
Notifications
You must be signed in to change notification settings - Fork 77
Build System Tweaks #706
Build System Tweaks #706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm overall
| - Updated the `MobileWorkerConnector` to use the KCP network protocol by default. | ||
| - Changed the `mobile_launch.json` config to use the new Runtime. | ||
| - Updated all the launch configs to use the new Runtime. | ||
| - Changed the way builds are processed in the Unity Editor. If you don't have build support for a particular target, that specific build target will be skipped rather than the whole build process cancelled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we drop the first sentence and just say something like "Changed the Unity Editor building process to skip builds with missing targets"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be cheeky and change it in #705 so I don't have to rerun CI here 😛
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless people have code concerns
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ran it, it works. thanks for the last minute change ❤️
Description
A last minute addition to the
0.1.4releasegrumble grumble- adjusting the build system to skip builds that you don't have build support for (without cancelling the other builds).For example - if you build all workers without mobile support installed you would get the following messages in the console.
Also the static
Buildmethod still throws if build support is missing (such that the process actually returns an error exit code) - so that behavior is unchanged.Tests
Tested a build locally and via command line.
Documentation
How is this documented (for example: release note, upgrade guide, feature page, in-code documentation)?
Did you remember a changelog entry?
Yes
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.
@jessicafalk @jared-improbable