-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Artifacts #2
Comments
Unifying native artifacts should be a simple solution. File bootclasspath.sh is created to ease inegration of native libraries that are present on device. |
Reference https://developers.google.com/apps-script/guides/libraries |
Commit 6554e05 adds a couple more places to place artifacts so they can be loaded into the build.
|
Commit 5343925 creates a simple way to add artifacts and libraries into the compilation. Change the first line of file .conf/LIBAUTH to |
Commit 95ab179 contains artifact search paths. Modify array |
old issue sanse activity message |
Adding libraries and artifacts is important to build many Android Aplication Kits. The method of adding libraries is one of a few ways to resolve building source code that depends on libraries and artifacts. This issues is devoted to modifying build.one.bash, build.sh and build.zsh so these scripts can parse the APK project configuration file(s) and add the desired components for a succeccfull build on device.
The text was updated successfully, but these errors were encountered: