react-native/local-cli/templates/HelloWorld/android/app/build.gradle

151 lines
5.9 KiB
Groovy
Raw Normal View History

apply plugin: "com.android.application"
import com.android.build.OutputFile
/**
* The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
* and bundleReleaseJsAndAssets).
* These basically call `react-native bundle` with the correct arguments during the Android build
* cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
* bundle directly from the development server. Below you can see all the possible configurations
* and their defaults. If you decide to add a configuration block, make sure to add it before the
* `apply from: "../../node_modules/react-native/react.gradle"` line.
*
* project.ext.react = [
* // the name of the generated asset file containing your JS bundle
* bundleAssetName: "index.android.bundle",
*
* // the entry file for bundle generation
* entryFile: "index.android.js",
*
* // whether to bundle JS and assets in debug mode
* bundleInDebug: false,
*
* // whether to bundle JS and assets in release mode
* bundleInRelease: true,
*
* // whether to bundle JS and assets in another build variant (if configured).
* // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
* // The configuration property can be in the following formats
* // 'bundleIn${productFlavor}${buildType}'
* // 'bundleIn${buildType}'
* // bundleInFreeDebug: true,
* // bundleInPaidRelease: true,
* // bundleInBeta: true,
*
* // whether to disable dev mode in custom build variants (by default only disabled in release)
* // for example: to disable dev mode in the staging build type (if configured)
* devDisabledInStaging: true,
* // The configuration property can be in the following formats
* // 'devDisabledIn${productFlavor}${buildType}'
* // 'devDisabledIn${buildType}'
*
* // the root of your project, i.e. where "package.json" lives
* root: "../../",
*
* // where to put the JS bundle asset in debug mode
* jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
*
* // where to put the JS bundle asset in release mode
* jsBundleDirRelease: "$buildDir/intermediates/assets/release",
*
* // where to put drawable resources / React Native assets, e.g. the ones you use via
* // require('./image.png')), in debug mode
* resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
*
* // where to put drawable resources / React Native assets, e.g. the ones you use via
* // require('./image.png')), in release mode
* resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
*
* // by default the gradle tasks are skipped if none of the JS files or assets change; this means
* // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
* // date; if you have any other folders that you want to ignore for performance reasons (gradle
* // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
* // for example, you might want to remove it from here.
* inputExcludes: ["android/**", "ios/**"],
*
* // override which node gets called and with what additional arguments
* nodeExecutableAndArgs: ["node"],
*
* // supply additional arguments to the packager
* extraPackagerArgs: []
* ]
*/
Move HelloWorld template to a single index.js entry point Summary: This change (initially discussed in https://github.com/react-community/create-react-native-app/issues/26) moves the HelloWorld project template from two nearly identical entry points (`index.android.js` and `index.ios.js`) to a single, minimal `index.js` entry point. The root component is created in `App.js`. This unifies the project structure between `react-native init` and Create React Native App and allows CRNA's eject to use the entry point from the HelloWorld template without any hacks to customize it. Also examples in the docs can be just copy-pasted to `App.js` the same way in both HelloWorld and CRNA apps without having to first learn about `AppRegistry.registerComponent`. * Created a new project from the template using `./scripts/test-manual-e2e.sh` and verified that: * The app builds, starts and runs both on Android and iOS. * Editing and reloading changes works. * The new files (`index.js`, `App.js`, `__tests__/App.js`) get created in the project folder. <img width="559" alt="screen shot 2017-08-01 at 19 10 51" src="https://user-images.githubusercontent.com/497214/28835171-300a12b6-76ed-11e7-81b2-623639c3b8f6.png"> <img width="467" alt="screen shot 2017-08-01 at 19 09 12" src="https://user-images.githubusercontent.com/497214/28835180-33d285e0-76ed-11e7-8d68-2b3bc44bf585.png"> <!-- Thank you for sending the PR! If you changed any code, please provide us with clear instructions on how you verified your changes work. In other words, a test plan is *required*. Bonus points for screenshots and videos! Please read the Contribution Guidelines at https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md to learn more about contributing to React Native. Happy contributing! --> Closes https://github.com/facebook/react-native/pull/15312 Differential Revision: D5556276 Pulled By: hramos fbshipit-source-id: 068fdf7e51381c2bc50321522f2be0db47296c5e
2017-08-03 20:52:06 +00:00
project.ext.react = [
entryFile: "index.js"
]
apply from: "../../node_modules/react-native/react.gradle"
/**
Consume Android artifacts from npm Summary: This lets us say goodbye to Maven Central. This will greatly simplify and speed up the release process as releasing Android artifacts to Maven Central adds a lot of [complexity](https://github.com/facebook/react-native/blob/master/Releases-publish.md) and delays the whole release by several hours when we have to wait for the artifacts to propagate. This diff assumes there's a local Maven repo at `node_modules/react-native/android`. The second part once this lands is to change our `release.sh` script to output the artifacts under `react-native/android` before publishing to npm. This adds 3.7MB to the size of `node_modules` of any app. However, we just download eagerly what we'd normally download later via Gradle. **Test plan** Released RN including a local Maven repo into Sinopia: $ cd react-native # Updated version in gradle.properties to 0.21.0 $ ./gradlew ReactAndroid:installArchives # Moved everything in .m2/repository/com/facebook/react to react-native/android $ ls react-native/android com/facebook/react/react-native/0.21.0/react-native-0.21.0.aar com/facebook/react/react-native/0.21.0/react-native-0.21.0.pom com/facebook/react/react-native/maven-metadata.xml ... # Set version in package.json to 0.21.0 $ npm set registry http://localhost:4873/ $ npm publish Created and ran an app: $ cd /tmp $ react-native init AndroidNpm $ cd AndroidNpm $ react-native run-android It worked. Checked that we're using the artifacts from node_modules/react-native/android: $ cd android $ ./gradlew app:dependencies compile - Classpath for compiling the main sources. +--- com.android.support:appcompat-v7:23.0.1 | \--- com.android.support:support-v4:23.0.1 | \--- com.android.support:support-annotations:23.0.1 \--- com.facebook.react:react-native:+ -> 0.21.0 +--- com.google.code.findbugs:jsr305:3.0.0 +--- com.facebook.stetho:stetho-okhttp:1.2.0 ... Checked that Android Studio can find the source jars (you can navigate to RN sources in Android Studio). Opened the new project as described in the [docs](https://facebook.github.io/react-native/docs/android-setup.html#editing-your-app-s-java-code-in-android-studio). public Reviewed By: bestander Differential Revision: D2912557 fb-gh-sync-id: 251c180518a3fb9bb8e80963b236e982d65533be shipit-source-id: 251c180518a3fb9bb8e80963b236e982d65533be
2016-02-09 14:36:30 +00:00
* Set this to true to create two separate APKs instead of one:
* - An APK that only works on ARM devices
* - An APK that only works on x86 devices
* The advantage is the size of the APK is reduced by about 4MB.
* Upload all the APKs to the Play Store and people will download
* the correct one based on the CPU architecture of their device.
*/
def enableSeparateBuildPerCPUArchitecture = false
/**
* Run Proguard to shrink the Java bytecode in release builds.
*/
def enableProguardInReleaseBuilds = false
android {
compileSdkVersion rootProject.ext.compileSdkVersion
buildToolsVersion rootProject.ext.buildToolsVersion
defaultConfig {
applicationId "com.helloworld"
minSdkVersion rootProject.ext.minSdkVersion
targetSdkVersion rootProject.ext.targetSdkVersion
versionCode 1
versionName "1.0"
ndk {
abiFilters "armeabi-v7a", "x86"
}
}
splits {
abi {
reset()
Consume Android artifacts from npm Summary: This lets us say goodbye to Maven Central. This will greatly simplify and speed up the release process as releasing Android artifacts to Maven Central adds a lot of [complexity](https://github.com/facebook/react-native/blob/master/Releases-publish.md) and delays the whole release by several hours when we have to wait for the artifacts to propagate. This diff assumes there's a local Maven repo at `node_modules/react-native/android`. The second part once this lands is to change our `release.sh` script to output the artifacts under `react-native/android` before publishing to npm. This adds 3.7MB to the size of `node_modules` of any app. However, we just download eagerly what we'd normally download later via Gradle. **Test plan** Released RN including a local Maven repo into Sinopia: $ cd react-native # Updated version in gradle.properties to 0.21.0 $ ./gradlew ReactAndroid:installArchives # Moved everything in .m2/repository/com/facebook/react to react-native/android $ ls react-native/android com/facebook/react/react-native/0.21.0/react-native-0.21.0.aar com/facebook/react/react-native/0.21.0/react-native-0.21.0.pom com/facebook/react/react-native/maven-metadata.xml ... # Set version in package.json to 0.21.0 $ npm set registry http://localhost:4873/ $ npm publish Created and ran an app: $ cd /tmp $ react-native init AndroidNpm $ cd AndroidNpm $ react-native run-android It worked. Checked that we're using the artifacts from node_modules/react-native/android: $ cd android $ ./gradlew app:dependencies compile - Classpath for compiling the main sources. +--- com.android.support:appcompat-v7:23.0.1 | \--- com.android.support:support-v4:23.0.1 | \--- com.android.support:support-annotations:23.0.1 \--- com.facebook.react:react-native:+ -> 0.21.0 +--- com.google.code.findbugs:jsr305:3.0.0 +--- com.facebook.stetho:stetho-okhttp:1.2.0 ... Checked that Android Studio can find the source jars (you can navigate to RN sources in Android Studio). Opened the new project as described in the [docs](https://facebook.github.io/react-native/docs/android-setup.html#editing-your-app-s-java-code-in-android-studio). public Reviewed By: bestander Differential Revision: D2912557 fb-gh-sync-id: 251c180518a3fb9bb8e80963b236e982d65533be shipit-source-id: 251c180518a3fb9bb8e80963b236e982d65533be
2016-02-09 14:36:30 +00:00
enable enableSeparateBuildPerCPUArchitecture
universalApk false // If true, also generate a universal APK
include "armeabi-v7a", "x86"
}
}
buildTypes {
release {
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
}
}
// applicationVariants are e.g. debug, release
applicationVariants.all { variant ->
variant.outputs.each { output ->
// For each separate APK per architecture, set a unique version code as described here:
// http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
def versionCodes = ["armeabi-v7a":1, "x86":2]
def abi = output.getFilter(OutputFile.ABI)
if (abi != null) { // null for the universal-debug, universal-release variants
output.versionCodeOverride =
versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
}
}
}
}
dependencies {
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
implementation "com.facebook.react:react-native:+" // From node_modules
}
// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
from configurations.compile
into 'libs'
}