-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Calling compile-android.sh from other directory fails #213
Comments
I went into the build folder manually and ran the command with the correct PATH, and it worked... (maybe because of the "Please run the same make command again" message?)
I'm absolutely clueless why this happens... It's like |
I'm tempted to work around this by uploading artifacts from aw-server-rust CI (#214) and then downloading them in aw-android CI using something like https://github.com/dawidd6/action-download-artifact (would require completing migration to GitHub Actions). Currently, aw-server-rust binaries are build in debug mode in CI. Perhaps switch to release mode for the master branch and aw-android CI can pick them up from there? |
Seems very strange to always have to point out a remote binary for aw-server, wouldn't that be quite annoying if you had to test changes in aw-server-rust with it? |
When trying to run
cd aw-server-rust && ./compile-android.sh
from the aw-android repo it fails when trying to buildopenssl-sys
, but if I run./compile-android.sh
directly from the aw-android folder it succeeds. Wtf?I've tried various different ways to compile it from the aw-android repo (like wrapping it in a Makefile target), but it just doesn't work...
The text was updated successfully, but these errors were encountered: