I think for many situations the SDK's library project mechanism
solves the originally posted problem (without additional plug-ins,
scripts, or the ant learning curve)...
http://developer.android.com/intl/fr/guide/developing/eclipse-adt.html#libraryProject
There is an ongoing thread in this group
android-developers@googlegroups.com
Sent: 2010 May, Sun, 23 15:55:09 GMT+00:00
Subject: [android-developers] Re: Best practices for creating multiple app
versions from a single codebase?
I think for many situations the SDK's library project mechanism
solves the originally posted problem (without
Hi Bob,
I too would be very interested to hear how you have your build process
setup.
Ideally I would like to develop and debug with Eclipse, commit my code
and then like you say, checkout a pristine copy and do production
builds of paid and free versions with a script.
If you get time to write
Here's how I did it, not sure if it is the best practice or the most
efficient one.
1. Create an Android project from Eclipse, this will be used solely
for developing paid version.
2. Create an ant script to copy the entire paid version to a separate
directory that becomes the free version.
3.
I don't recommend doing production builds directly in your Eclipse
environment.
Export a copy, and modify that. In fact, I strongly urge checking out
a pristine copy from revision control for real production builds.
I derive my build numbers from the Eclipse revision I'm building. I
inject that
Hi, Bob.
A description of best build practices would be pure gold to me. I'm
nearing an application release (this month I hope) but have not yet
ventured beyond building it with Eclipse.
- Greg
On May 7, 11:25 am, Bob Kerns r...@acm.org wrote:
I don't recommend doing production builds
I agree with Bob on this, you should be able to build your system for
release outside of Eclipse entirely, there should be no dependencies
at all with that environment. A good way to set this up is to use a
Continuous Integration Server like Hudson to do this. There are even
Hudson plugins that
On Fri, May 7, 2010 at 12:13 PM, Alex (PS3 Friends) kludg...@gmail.com wrote:
it also makes it easier to
move from one machine to another if need be
Just curious.. what problems have you ran into developing across
multiple machines? I develop on both Win7 and Ubuntu Linux using git
and I have
I am using the Eclipse tool also, I feel your pain with not being able
to use Netbeans as natively as Eclipse, Eclipse is a great tool,
just really used to Netbeans. It has been a while but I believe I
created the project using the Eclipse tool. You can then create the
ant script using the
Thanks. I am surprised there isn't built in support for auto build
numbers as it's very useful.
Leigh
On 5/5/2010 9:41 AM, Alex (PS3 Friends) wrote:
I am using the Eclipse tool also, I feel your pain with not being able
to use Netbeans as natively as Eclipse, Eclipse is a great tool,
just
I'm thinking about the same thing.
I believe that http://code.google.com/p/maven-android-plugin/ could be
a solution. Maven is very powerful tool for building (we are using it
for JEE projects) so I'm sure that it will support also multiple APKs
from one source code base.
But I didn't looked
My solution was to create two different starter classes with different
packages. One for the paid version and the other for the free
version. Since the package name is used to identify the application
in the market. You can use this to customize the app, by setting
properties in the different
Since you talk about a generated ant file tt sounds like you're project
was created using the android tool instead of Eclipse. Is this
correct? I spent most of today trying to get a non-eclipse project
going and had some success up until debugging. I really wanted to use
NetBeans but it
13 matches
Mail list logo
