Build.gradle無法正常化文件的路徑

Question

在嘗試構建我的應用程序時，發生在React Native中，但我覺得它是一個全能的gradle問題。基本上，它似乎是實際的SDK的路徑是錯誤的..我正在運行Windows，並有我的路徑存儲在「ANDROID_HOME」環境變量的SDK。

* Where: 
Build file 'D:\PackBar\android\app\build.gradle' line: 104 

* What went wrong: 
A problem occurred evaluating project ':app'. 
Could not normalize path for file 'D:\PackBar\android\D:Android_SDK\tools\proguard\proguard-android.txt'. 

出於某種原因，使得這個路徑： 'd：\ PackBar \機器人\ d：Android_SDK \工具\ proguard的\ proguard的-android.txt'

很明顯，你可以看到在d：\兩次..明顯錯誤..我的sdk的ACTUAL路徑是：D：Android_SDK \ tools \ proguard \ proguard-android.txt'

我想我的問題的簡化版本是如何更改此路徑？

編輯：這裏是我的APP.GRADLE

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, 
* 
* // 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/**"] 
* ] 
*/ 

apply from: "../../node_modules/react-native/react.gradle" 

/** 
* 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 23 
    buildToolsVersion "23.0.1" 

    defaultConfig { 
     applicationId "com.packbar" 
     minSdkVersion 16 
     targetSdkVersion 22 
     versionCode 1 
     versionName "1.0" 
     ndk { 
      abiFilters "armeabi-v7a", "x86" 
     } 
    } 
    splits { 
     abi { 
      reset() 
      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 { 
    compile fileTree(dir: "libs", include: ["*.jar"]) 
    compile "com.android.support:appcompat-v7:23.0.1" 
    compile "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' 
} 

Answer 1

我有同樣的問題，什麼固定它對於我來說是：

我的環境：Windows 10，64位機

1. 我安裝了最新的JDK。 （JDK-8u101窗口-64）（之前我已經安裝了1.7）
2. 新增的環境變量JAVA_HOME = C：\ Program Files文件\的Java \ jdk1.8.0_101（默認路徑安裝，而在我的情況）
3. 新增％ JAVA_HOME％\ bin到PATH環境變量。
4. 從新項目開始。與react-native init newproj。

我不會說這是一個答案，但請嘗試，如果你還沒有。我希望它有幫助。