Hello!

I made some changes to the Android 2.3.3 (API 10) framework and added
new functionality like support for ethernet, i2c, uart, gpio ...

To make the user able to use theese functionality I built a new
Android SDK simply with "make sdk". So I got a new folder "sdk" in
android-2.3.3_r1/out/host/linux-x86.
Because our customers are working with Windows I copied the
android-2.3.3 folder from the platforms directory into the platforms
directory of my Android SDK under Windows. The new platform appears in
Eclipse and new applications are able to make use of the new API.
Theese apps are also running on the real hardware without any
problems.

The problem now is that this procedure is not working anymore when the
platforms directory of my Windows SDK contains another platform with
the same API level (the original and non-edited Android 2.3.3, in my
case called android-10).

So I tried something else. I created a SDK add-on that makes use of
the standard Android platform with API level 10 and includes libraries
(jar) to include the additional functionality. This is working for all
packages that I've added completely new to the framework. But of
course I had to modify also classes that are existing in the standard
platform. Theese changes are not recognized in Eclipse.

Excerpt from my hardware.ini in my add-on:

# list of libraries, separated by a semi-colon.
libraries=android.net.ethernet;android.content

# details for each library
android.net.ethernet=android-2.3.3-guf.jar;WORKING!
android.content=android-2.3.3-guf.jar;NOT WORKING!

In this example all functionality of my ethernet package can be used,
but one needed static variable that finds in
android.content.Context(.java) is marked red in Eclipse. I think
because this class is already existing in the standard Android
platform.

Does someone have an idea how this problem can be solved? Thanks a lot!

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to