Thanks for the follow up Xavier - Things are a little clearer now... So first off, to answer your question - we are currently doing internal development where we are working against a 'tweaked' android platform (r8). The reason for the tweaks is basically to accommodate some unique hardware features of a device under development that don't quite mesh with some of the stock android APIs. This is not really 'add-on' behavior (as is seen in something like the google mapping api) but rather a drop-in replacement to get some specific behavior.
That being said, one of our ultimate goals if of course to achieve full compatibility through the application of the CDD/CTS so we'll have to look at how we can achieve that goal. If you have any suggestions, I'm all ears ;) Back to the issue at hand though, so to accommodate our internal development, am I correct in assuming that we must rebuild the SDK/AVD manager using a custom URL that will replace the current constant in SdkRepoContants as indicated below: 29 /** The URL of the official Google sdk-repository site. */\r 30 public static final String URL_GOOGLE_SDK_SITE =\r 31 "https://dl-ssl.google.com/android/ repository/"; //$NON-NLS-1$\r And of course, publish a repository.xml that conforms to the schema (#3) to exposes our platform/samples/docs etc? Thanks again for your assistance. Todd On Dec 13, 4:55 pm, Xavier Ducrohet <x...@android.com> wrote: > Hi > > We don't have docs for this at the moment, but I'll give you a few pointers. > > First a question, through: why do you want to publish a repo for > "custom platform based stock android" ? > > If you want to extend only android you should do so through optional > libraries (similar to the map view library), which are distributed > through add-ons. Look at vendor/sample in the git repositories for an > example of a platform library available to dev and an add-on that > exposes it. > > Of course if this is for internal use that's a different matter. Note > however that the SDK updater has 2 built-in repositories: the main > repositories and a list of add-ons repositories. You'll want to > distribute a custom SDK Updater to your users with different default > repositories. > > Now, the 3 schemas are available > at:http://android.git.kernel.org/?p=platform/sdk.git;a=tree;f=sdkmanager... > > The way we generate various package is pretty basic. "make sdk" makes > a generic SDK with all components which we extract and rezip only the > components we want: docs (content of docs/), samples (content of > samples/android-#), platform (content of platforms/android-#), etc... > > Xav > > > > > > > > > > On Fri, Dec 10, 2010 at 6:19 AM, todd.lee <todd....@ca.flextronics.com> wrote: > > I'm new to the group and just looking for some information on > > publishing our own repository that the SDK manager can access. > > We're looking to distribute the following: > > > - custom platform based stock android > > - addon library > > - images for custom emulator > > - offline docs > > - sample code > > > I've been able to piece a few things together from looking at the > > structure of the repository.xml file > > athttps://dl-ssl.google.com/android/repository/repository.xml, > > but I wonder if there is any formal docs that I can look at that would > > help us to understand what we need to put in place. Specifically, I > > noticed that the 'About' info on the SDK Manager for Revision 8 > > references the following: > > > Add-on XML Schema #1 > > Repository XML Schema #3 > > > Can someone fill in the blanks her (or point me in the right direction > > at least ;) ) > > > Many thanks. > > Todd > > > -- > > unsubscribe: android-porting+unsubscr...@googlegroups.com > > website:http://groups.google.com/group/android-porting > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. > > Please do not send me questions directly. Thanks! -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
