Home/ Questions/Q 6678107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T04:12:13+00:00

I would like an Android build system procedure, command line or Eclipse, to generate

  • 0

I would like an Android build system procedure, command line or Eclipse, to generate several .apk files from a single source codebase. Some common reasons for this – having specific versions for markets with different requirements or a free and paid version.

This question IS NOT ABOUT:

Google says “you probably need to create separate Android projects for each APK you intend to publish so that you can appropriately develop them separately. You can do this by simply duplicating your existing project and give it a new name.” Then they kindly suggest using libraries, which I understand. Then, they mention in passing exactly what I do want: “a build system that can output different resources based on the build configuration”

  • I know that to accomplish conditional compilation in JAVA one can key off a ‘public static final’ variable. There is an example of tweaking such a value in build.xml. Any more complete example of an Android Ant build configuration for this or a link to an OSS project doing that now, please? BTW, build.xml is auto-generated, but I have seen people hacking it, so how does that work?

  • With the package name declared in Manifest.xml as package=”com.example.appname”, if one needs to emit multiple .apks that vary that name, is one stuck with a separate project for each?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m generating 2 different APK’s (demo and production) from one single source tree with 3 small modifications:

    1) I have public static final DEMO=true; //false; in my Application class and depending on that value I used to switch code between demo/production features

    2) There are 2 main activities, like:

    package mypackage;
public class MyProduction extends Activity 
{
    //blah-blah
}

package mypackage.demo;
public class MyDemoActivity extends mypackage.MyProductionActivity
{
    //blah-blah
}

    3) And in the end 2 separate AndroidManifest.xml files which points to different launcher activities depending on demo/production switch

    I’m switching between 2 APK’s manually, but see nothing difficult in writing small ANT task to switch between them automatically

    • 0