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.

Sign up for GitHub

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

gradle build file #227

Open
wants to merge 1 commit into
base: GLES2-AnchorCenter
Choose a base branch
from
Open

gradle build file #227

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,5 +26,7 @@ gdbserver
.settings

# IntelliJ / Android Studio:
build/
idea/workspace.xml
idea/tasks.xml
idea/tasks.xml
*.iml
Copy link
Owner

Choose a reason for hiding this comment

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

Is there a reason not include the iml project file?

Copy link
Author

Choose a reason for hiding this comment

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

unfortunately it seems to include project specific values e.g. the :Submodules:AndEngine below.

<facet type="android-gradle" name="Android-Gradle">
  <configuration>
    <option name="GRADLE_PROJECT_PATH" value=":Submodules:AndEngine" />
    <option name="PROJECT_ABSOLUTE_PATH" value="$MODULE_DIR$/../.." />
    <option name="GRADLE_HOME_DIR_PATH" />
  </configuration>
</facet>

i imagine there's some things to be worked out with how things are setup with gradle and android studio. i'm not sure if they intend the iml files to be committed or not to be honest. i've seen them ignored in other projects... there's nothing really important in them at this point, you can just get it in to your project and working by importing module in the project settings dialog. that said it isn't completely hooked up to the build.gradle and settings.gradle files so there's a couple things you have to do there.

in my case i had to add the following to settings.gradle:

include ':Submodules:AndEngine'

and the following line to the dependencies section of build.gradle in my app's file:

compile project(':Submodules:AndEngine')

i assume those two tweaks will go away once gradle and android studio are fully cooperating. perhaps they're some tweaks needed to the iml files as well to avoid needing GRADLE_PROJECT_PATH. if i take that out currently gradle barfs on me...

37 changes: 37 additions & 0 deletions build.gradle
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
buildscript {
repositories {
maven { url 'http://repo1.maven.org/maven2' }
}

dependencies {
classpath 'com.android.tools.build:gradle:0.4'
}
}

apply plugin: 'android-library'

android {
compileSdkVersion 17
buildToolsVersion "17.0.0"

defaultConfig {
minSdkVersion 10
targetSdkVersion 16
}

sourceSets {
main {
manifest.srcFile 'AndroidManifest.xml'
java.srcDirs = ['src']
resources.srcDirs = ['src']
aidl.srcDirs = ['src']
renderscript.srcDirs = ['src']
res.srcDirs = ['res']
assets.srcDirs = ['assets']
}

instrumentTest.setRoot('tests')
}


}