Assuming your lib is written in Java you simply create a normal Java application in Eclipse and let it have a dependency to the lowest Android platform jar you want to support. In your Android project you can then either directly reference the common library project or generate a jar from the library project which you make the Android project dependent on. The Android platform jar can be found in the SDK folder.
If your lib is written in C/C++ (which i actually assume as you said you move over from the IPhone) then you can again create a seperate project in Eclipse, put a jni/ folder in it that houses all your C/C++ code along with an Android.mk for the build rules. There's ways to directly compile in Eclipse, i suggest googling for "cdt android ndk". The problem will be that you will need to copy the shared library over to your Android project each time it is rebuild. This can be automated to some extend but will probably result in hardcoding a path to write the shared library file to in some script, not the nicest solution. Getting the ADT plugin to copy over the libs/armeabi folder from a referenced project to an Android project does not work yet which is a bit of a bummer. hth On 14 Apr., 20:38, scott <[email protected]> wrote: > I am currently moving from Xcode and iPhone development to Android > with Eclipse. I want to have a shared code project so that I can store > all the code to be shared across apps in one common library. However > it would appear that the only android project available is for > applications and not for code libs how can i achieve this? -- 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.
