build.xmlとproject_name.xmlの違い

Question

私は何時間もAndroidのビルドプロセスを理解しようとしています。

私はIntelliJ Idea for Androidを使用しています（素晴らしいツールです）。私はIntelliJという名前のテストプロジェクトを "Hello Android"という名前でオープンしました。複数ファイルのAntビルドを生成> Antビルドを生成し、

1. 次のオプションを選択 - プロジェクトはその後、私はIntelliJのアイデアビルドには、以下のなかった、

   <?xml version="1.0" encoding="UTF-8"?> 
   <project name="HelloAndroid" default="help"> 
   
       <!-- The local.properties file is created and updated by the 'android' tool. 
        It contains the path to the SDK. It should *NOT* be checked into 
        Version Control Systems. --> 
       <property file="local.properties" /> 
   
       <!-- The ant.properties file can be created by you. It is only edited by the 
        'android' tool to add properties to it. 
        This is the place to change some Ant specific build properties. 
        Here are some properties you may want to change/update: 
   
        source.dir 
         The name of the source directory. Default is 'src'. 
        out.dir 
         The name of the output directory. Default is 'bin'. 
   
        For other overridable properties, look at the beginning of the rules 
        files in the SDK, at tools/ant/build.xml 
   
        Properties related to the SDK location or the project target should 
        be updated using the 'android' tool with the 'update' action. 
   
        This file is an integral part of the build system for your 
        application and should be checked into Version Control Systems. 
   
        --> 
       <property file="ant.properties" /> 
   
       <!-- if sdk.dir was not set from one of the property file, then 
        get it from the ANDROID_HOME env var. 
        This must be done before we load project.properties since 
        the proguard config can use sdk.dir --> 
       <property environment="env" /> 
       <condition property="sdk.dir" value="${env.ANDROID_HOME}"> 
        <isset property="env.ANDROID_HOME" /> 
       </condition> 
   
       <!-- The project.properties file is created and updated by the 'android' 
        tool, as well as ADT. 
   
        This contains project specific properties such as project target, and library 
        dependencies. Lower level build properties are stored in ant.properties 
        (or in .classpath for Eclipse projects). 
   
        This file is an integral part of the build system for your 
        application and should be checked into Version Control Systems. --> 
       <loadproperties srcFile="project.properties" /> 
   
       <!-- quick check on sdk.dir --> 
       <fail 
         message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable." 
         unless="sdk.dir" 
       /> 
   
       <!-- 
        Import per project custom build rules if present at the root of the project. 
        This is the place to put custom intermediary targets such as: 
         -pre-build 
         -pre-compile 
         -post-compile (This is typically used for code obfuscation. 
             Compiled code location: ${out.classes.absolute.dir} 
             If this is not done in place, override ${out.dex.input.absolute.dir}) 
         -post-package 
         -post-build 
         -pre-clean 
       --> 
       <import file="custom_rules.xml" optional="true" /> 
   
       <!-- Import the actual build file. 
   
        To customize existing targets, there are two options: 
        - Customize only one target: 
         - copy/paste the target into this file, *before* the 
          <import> task. 
         - customize it to your needs. 
        - Customize the whole content of build.xml 
         - copy/paste the content of the rules files (minus the top node) 
          into this file, replacing the <import> task. 
         - customize to your needs. 
   
        *********************** 
        ****** IMPORTANT ****** 
        *********************** 
        In all cases you must update the value of version-tag below to read 'custom' instead of an integer, 
        in order to avoid having your file be overridden by tools such as "android update project" 
       --> 
       <!-- version-tag: 1 --> 
       <import file="${sdk.dir}/tools/ant/build.xml" /> 
   
   </project> 
   

   以下のコードをこのファイル名build.xmlを持っています

2. 出力ファイル名：helloandroid
3. UIはコンパイル
4. 使用JSDK definを形成して有効にします

プロジェクトファイルからitionsこれは、三つの追加のファイル

1. helloandroid.properties
2. helloandroid.xml
3. module_helloandroid.xml

helloandroid.propertiesの創造の結果

path.variable.maven_repository=C\:\\Users\\abc\\.m2\\repository 
jdk.home.android_4.1_platform=C\:/Program Files (x86)/Android/android-sdk 

helloandroid.xml

<?xml version="1.0" encoding="UTF-8"?> 
<project name="HelloAndroid" default="help"> 

    <!-- The local.properties file is created and updated by the 'android' tool. 
     It contains the path to the SDK. It should *NOT* be checked into 
     Version Control Systems. --> 
    <property file="local.properties" /> 

    <!-- The ant.properties file can be created by you. It is only edited by the 
     'android' tool to add properties to it. 
     This is the place to change some Ant specific build properties. 
     Here are some properties you may want to change/update: 

     source.dir 
      The name of the source directory. Default is 'src'. 
     out.dir 
      The name of the output directory. Default is 'bin'. 

     For other overridable properties, look at the beginning of the rules 
     files in the SDK, at tools/ant/build.xml 

     Properties related to the SDK location or the project target should 
     be updated using the 'android' tool with the 'update' action. 

     This file is an integral part of the build system for your 
     application and should be checked into Version Control Systems. 

     --> 
    <property file="ant.properties" /> 

    <!-- if sdk.dir was not set from one of the property file, then 
     get it from the ANDROID_HOME env var. 
     This must be done before we load project.properties since 
     the proguard config can use sdk.dir --> 
    <property environment="env" /> 
    <condition property="sdk.dir" value="${env.ANDROID_HOME}"> 
     <isset property="env.ANDROID_HOME" /> 
    </condition> 

    <!-- The project.properties file is created and updated by the 'android' 
     tool, as well as ADT. 

     This contains project specific properties such as project target, and library 
     dependencies. Lower level build properties are stored in ant.properties 
     (or in .classpath for Eclipse projects). 

     This file is an integral part of the build system for your 
     application and should be checked into Version Control Systems. --> 
    <loadproperties srcFile="project.properties" /> 

    <!-- quick check on sdk.dir --> 
    <fail 
      message="sdk.dir is missing. Make sure to generate local.properties using 'android update project' or to inject it through the ANDROID_HOME environment variable." 
      unless="sdk.dir" 
    /> 

    <!-- 
     Import per project custom build rules if present at the root of the project. 
     This is the place to put custom intermediary targets such as: 
      -pre-build 
      -pre-compile 
      -post-compile (This is typically used for code obfuscation. 
          Compiled code location: ${out.classes.absolute.dir} 
          If this is not done in place, override ${out.dex.input.absolute.dir}) 
      -post-package 
      -post-build 
      -pre-clean 
    --> 
    <import file="custom_rules.xml" optional="true" /> 

    <!-- Import the actual build file. 

     To customize existing targets, there are two options: 
     - Customize only one target: 
      - copy/paste the target into this file, *before* the 
       <import> task. 
      - customize it to your needs. 
     - Customize the whole content of build.xml 
      - copy/paste the content of the rules files (minus the top node) 
       into this file, replacing the <import> task. 
      - customize to your needs. 

     *********************** 
     ****** IMPORTANT ****** 
     *********************** 
     In all cases you must update the value of version-tag below to read 'custom' instead of an integer, 
     in order to avoid having your file be overridden by tools such as "android update project" 
    --> 
    <!-- version-tag: 1 --> 
    <import file="${sdk.dir}/tools/ant/build.xml" /> 

</project> 

module_helloandroid。XML

<copy todir="${helloandroid.output.dir}"> 
    <fileset dir="${module.helloandroid.basedir}/src"> 
    <patternset refid="compiler.resources"/> 
    <type type="file"/> 
    <patternset refid="excluded.from.compilation.helloandroid"/> 
    </fileset> 
    <fileset dir="${module.helloandroid.basedir}/gen"> 
    <patternset refid="compiler.resources"/> 
    <type type="file"/> 
    <patternset refid="excluded.from.compilation.helloandroid"/> 
    </fileset> 
</copy> 

私の質問

1. 我々は異なるのbuild.xmlとhelloandroid.xmlや他の2つのファイルを持っているのはなぜ？
2. これらのファイルをビルドプロセスで使用できますか？
3. これらのファイルを編集して、さらにAntビルドスクリプトを追加できますか？
4. なぜbuild.xmlにenv.ANDROID_HOMEというエラーが表示されますか？
5. jdk.home.1.6にはどのhelloandroid.xmlがエラーを表示していますか？

Answer 1

1. 他のビルドファイルを含めることができるファイルを作成しますが、これは通常の練習です。プロジェクトのhelloandroid.xmlはbuild.xmlファイルとまったく同じです。好きなものを変更してもう一方を破棄することができます。Antの場合は、build.xmlファイルが優先されます。プロパティファイルはプロパティを設定するためのものであり、モジュールファイルは呼び出されないように見えますが、おそらくファイルファイルをインクルードして指定したとおりにファイルをコピーできるように存在しています。

2. はい、含めてください。汎用ファイルproject.propertiesの代わりにhelloandroid.propertiesファイルを使用することもできますが、そのままにしておくこともできます。

3. はい、簡単に始めるには十分ですが、編集してください。

4. あなたのANDROID_HOME環境変数が設定されていないようです。 IntelliJから設定することはできますが、OSレベルで行うことをお勧めします。

5. JAVA_HOME環境変数が設定されていないようです。 IntelliJから設定することはできますが、OSレベルで行うことをお勧めします。