What I did was to create a new project, with a new package name.
Then right-click on that project
go to properties
Then Android
Go to the bottom and click IsLibrary
I used the library activity as the main class and in the projects that use
the library I extend the library version.
You also need t
On Tue, Dec 27, 2011 at 9:54 AM, John Goche wrote:
> OK, so how do I set up an android library project then.
http://developer.android.com/guide/developing/projects/index.html#LibraryProjects
-
TreKi
On Tue, Dec 27, 2011 at 4:43 PM, TreKing wrote:
>
> Yes, but an Android Library Project will help consolidate the common code.
>
OK, so how do I set up an android library project then. Having to maintain
two separate source trees for every single application seems to be a pain.
Please share you
On Tue, Dec 27, 2011 at 9:29 AM, John Goche wrote:
> I was
> wondering, if my package name is com.bar.foo and my application
> name if com.bar.foo do I need to make a separate com.bar.foolite
> application name for the free version
>
You can have the same application name, but not the same packag
Hello,
I have an application which I would like to publish as a free version
and then another with some extra features as a paid version. I was
wondering, if my package name is com.bar.foo and my application
name if com.bar.foo do I need to make a separate com.bar.foolite
application name for the
5 matches
Mail list logo
