Skip to content
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

Tom #5

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Tom #5

wants to merge 2 commits into from

Conversation

TomKeel
Copy link

@TomKeel TomKeel commented Feb 11, 2013

These are the changes I made while working on porting GLib for the dLeyna project.

The first commit is so that I can easily build for (1) arm or x86 architecture, (2) a given Android API level, and (3) using a given version of the cross toolchain.

The second commit just removes zlib as a dependency of glib, since it's already supplied in the Android NDK.

This enables choosing to build
  - for ARM or x86
  - for a particular Android API level
  - using a particular version of the cross toolchain
by setting a few variables at the top of the build script.

This also allows specifying where to install the NDK and SDK by
setting variables at the top of the build script. The default is to
install them in the $HOME directory.
Because libz is in the Android NDK.
@ghost ghost assigned djdeath and thos Feb 12, 2013
export ANDROID_SDK_DIR="$PWD/android-sdk-linux"
export ANDROID_NDK_DIR=`find $PWD/* -maxdepth 0 -type d -name 'android-ndk-r*'`
export ANDROID_SDK_DIR="$HOME/android-sdk-linux"
export ANDROID_NDK_DIR=`find $HOME -maxdepth 1 -type d -name 'android-ndk-*'`
Copy link
Member

Choose a reason for hiding this comment

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

Some people may not want the Android SDK installed in their home directory, so I think this should be configurable if you want to specify a different location for the SDK and NDK.

@thos
Copy link
Member

thos commented Feb 12, 2013

Thanks for the patch. I've taken a look through and made a few suggestions above, but this is certainly a feature worth including.

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