I use a Git repo to manage all of my project's code. I store the meat of the code on GitHub, while I have local 'free' and 'donate' branches, each with slight modifications of their own. When the time comes to get a new release ready, I just merge the changes from the master branch into each of these local branches, fixing merge conflicts as they appear. Then I just export the application using Eclipse and I'm good to go.
On Apr 5, 11:37 pm, Marc <[email protected]> wrote: > I used to be a C/C++ programmer before getting in to android. I am not > sure how people maintain 2 versions of a program without using #ifdef > preprocessor macros. Right now I am changing the package name in > eclipse and changing the code manually, but this seems really > inefficient. Can anybody suggest a good way of having 2 or more > projects that share most of the code? -- 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 To unsubscribe, reply using "remove me" as the subject.
