Android commend build. xml

Generally, when Android programs are developed, eclispe is selected for zookeeper, but eclispe does not generate the build required by ant at the same time when it establishes an Android-related project. XML, so before we put it on Hudson, we must first generate the corresponding build. XML.

Google has always been a treasure and does not allow us to build our own images. XML is so painful and difficult, the method is very simple, that is, when we create a project by command, we will also generate the build we need. XML, instructions can be used to test the establishment of general cases, and the establishment of complex cases

Example:

Android Create project -- Target 4 -- name yourprojectname -- path yourprojectpath -- activity startupactivity -- package yourpackgename

-- Target indicates that the androdi version is used during the upgrade. -- Name indicates the case name. -- Path indicates the stored path in the hosts file. -- Activity indicates the starting activity. -- Package Java package name: volume

If you want to generate an android test project example, for example:

Android create test-project-M projectpath-N yourtestprojectname-P yourtestprojectpath

-- M: the number of records to be merged -- N indicates the case name -- P zhongkui Case Study

After the preceding commands are executed, you can obtain their own build. xml files. However, you may have discovered that the content of these two build. xml files is exactly the same?
Are you kidding Google ?? The content of the build. properties proposal generated at the same time,
If you generate a test project, build. properties will have tested. Project. dir = yourprojectpath to specify where the project to be merged is located,
Let's look at this small change. He decided which target should be used by the user at the time and which of the following can be used by the user.
After production, do not forget to add build. xml and build. properties to the source. The above is the step for the production build file.

Buils. xml