No, 99.44% of the code would be in the library. You need to implement
value of one constant in the code in each APK project, plus your
manifest to pick up your distinct packages.
Ok done. It was a bit of work to split my code, create new
repositories, etc etc, but it feels like a clean,
Maybe a buildr or gradle script to do it..
Buildr uses ruby and Gradle uses groovy
On Dec 19, 6:56 am, Mark Murphy mmur...@commonsware.com wrote:
Use an Android library project:
http://developer.android.com/guide/developing/eclipse-adt.html#librar...
It will not get down quite to the
It can be quite difficult to properly maintain two sets of code, but
it looks to me that your on the right track... At least as well as any
of us.
The market is shim ply not built to handle a free/paid version well.
It could be, but it doesn't seem to be a priority to the market folks.
The
Ok, I've tried the 'shell script' approach.
First, I tried to just manually adjust my project. So:
- I changed the value of 1 constant in my code which determines if it
builds into a lite or a full version
- I changed android:icon , android:label and 'package' in the manifest
- this forced me to
On Sun, Dec 19, 2010 at 12:58 PM, Utumno lkoltun...@gmail.com wrote:
'android library' - looks promising, although I already have
everything organised in such a way that all I have to do is change the
value of one constant in the code and everything else automatically
rebuilds into the proper
5 matches
Mail list logo
