Skip to content

Conversation

@ryantrem
Copy link
Member

@ryantrem ryantrem commented Jul 8, 2020

The main change here is to update publish.yml to now prep the environment for building source code, and then actually building the source using gulp, and finally publishing the binary package (instead of the source package). I've already created a release to test the full flow and the created package (https://www.npmjs.com/package/@babylonjs/react-native). I have one more package being built and published now, which updates the README.md to remove the steps that are no longer needed since the source is pre-compiled.

  • Update publish.yml to install Ninja, do a Yarn install on the Playground app (since we build it to produce the libBabylonNative.so files for Android), do a NPM install in the Package directory (to install a few tools and libraries needed for the Gulp build), then actually run the Gulp build, and finally publish the pre-compiled package instead of the source package.
  • Update the build.gradle files to switch to a different version of the NDK which is pre-installed on GitHub build agents (and update the associated documentation).
  • Update the package README.md to remove the steps that are no longer necessary with the pre-compiled package.

Additionally, since building the code is now relatively trivial, I am also adding pr.yml to facilitate gated PR builds. This duplicates steps from publish.yml as there doesn't seem to be any way to share a set of steps across jobs with GitHub Actions/Workflows, but the steps are really simple so meh.

ryantrem and others added 30 commits July 1, 2020 12:16
…e libs we care about into a single build directory
Create binary podspec

Update PackageTest app to use binary package
Clean up gulpfile
Remove Build.sh

Update Readme regarding creating packages
Fix NDK version in README.md
def DEFAULT_MIN_SDK_VERSION = 18
def DEFAULT_TARGET_SDK_VERSION = 28
def DEFAULT_NDK_VERSION = '21.0.6113669'
def DEFAULT_NDK_VERSION = '21.3.6528147'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, any reason we needed to update the NDK version?

Copy link
Contributor

@Alex-MSFT Alex-MSFT Jul 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah nevermind I reread the description, this is what is preinstalled on the Github build machines. This version seems relatively new, are we going to need to regularly update the NDK version to keep our PR builds working?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the PR description :) "Update the build.gradle files to switch to a different version of the NDK which is pre-installed on GitHub build agents"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I saw that, I was also wondering if this version is a moving target, are we going to need to periodically keep track and update this to keep our PR builds working?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know. I tried not specifying it, but then it just picked some default that is not installed on my machine or on the build agents. :(
As far as I can tell, there is not a way to say "use latest" or anything like that.

@ryantrem ryantrem merged commit 2f730da into master Jul 8, 2020
@ryantrem ryantrem deleted the binary-builds branch October 6, 2020 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants