You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
While building the web apps, one problem I have to keep dealing with is to select the 'final' apk from the 3 that are generated in outDir - usually I do 'ls -1 build/*.apk | grep -v signed'.
I find it would be preferable to put all the working files in different place, perhaps to be determined but a --temp arg?
The text was updated successfully, but these errors were encountered:
If you're using the API, the promise returned by the Env.build() method resolves to the path to the last file.
If you want to do it from within your task, you could just get that last output path and put the file somewhere else, leaving the other files in the build directory. So the build might go to build/artefacts and you move the final apk to build/, say.
But I quite like the idea of creating outDir/tmp/ for the build artefacts, and the final output apk just goes into outDir/.
Fair enough. I suppose grunt-crosswalk could set an 'outDir' to somewhere temporary, and then copy out the final apk into the 'outDir' set in the Gruntfile.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While building the web apps, one problem I have to keep dealing with is to select the 'final' apk from the 3 that are generated in outDir - usually I do 'ls -1 build/*.apk | grep -v signed'.
I find it would be preferable to put all the working files in different place, perhaps to be determined but a --temp arg?
The text was updated successfully, but these errors were encountered: