It'll be nice to have this info here as well http://developer.android.com/sdk/1.5_r1/upgrading.html#AntUsers
On Apr 14, 2:29 pm, Xavier Ducrohet <[email protected]> wrote: > Hello, > > The new SDK include multiple versions of the Android platforms. > Because newer versions could have slightly different build steps, we > have decide to keep most of the build logic inside the platforms > themselves. > > Thus, the new build.xml imports a file called android_rules.xml > located inside SDK/platforms/<platform>/templates/ (it might move in > the final SDK but you shouldn't care much). > > This file actually being imported is resolve in the first step of the > build. The custom task <setup /> looks at the value loaded from > "default.properties" which contains the target project (ie which > platform/add-on the project is compiling for), and then import the > proper rules file (after doing some properties init as well). > > If you want to change the rules to make them your own, I'd sugges to > leave android_rules.xml unchanged, and instead copy the rules inside > your build.xml file, *after* the <setup /> task. > Additionally, change the setup task to <setup import="false"/>. This > will let the custom task do the properties init but not do the import. > > Some of the target in the rules files are slightly different than > before, with some using custom tasks as well. This is due to a new > feature to generate multiple APKs from a single project (with > different resources). > You can either ignore this and reuse some of the previous target/task, > or modify the custom task to do what you want (we're pushing the > source used to generate this SDK on the git server today) > > Xav > > > > On Tue, Apr 14, 2009 at 9:50 AM, Ward Willats <[email protected]> wrote: > > > 'Round these parts we don't use Eclipse and heavily customize our > > build.xml file. The "android" tool tried to update it and burped out > > a short, confused file. > > > That's OK. Don't mind doing build.xml by hand and "target-ifying" it, > > but I see what look like a whole set of Android-specific ANT > > tasks/libs (prefs, apkbuilder, jarutil..), of which only <setup> went > > into the new build.xml. > > > So.....do I have to include any other custom ANT tasks besides > > <setup>? Or can I just use more-or-less the same command lines as > > before with aapt, javac, dx, etc...? > > > And what are these "rules" setup uses? And where are they included from? > > > Thanks > > > -- Ward > > -- > Xavier Ducrohet > Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
