Incredible what is happening.....incredible. Information weren't out of date, and now no information at all. And now we are waiting for Google to create new materials.....incredible. Something is changing; must we seriously think to an alternative?
N. On Apr 11, 4:24 pm, Sean Kelley <[email protected]> wrote: > Are Android's porting websites down? > > http://source.android.com/porting/ > > Gives me an error 404 > > On Apr 7, 1:25 pm, freakingtux <[email protected]> wrote: > > > Hello > > > I would like some information about porting to a new product. I am mainly > > interested in understanding the preferred directory layout > > to perform modifications to the system > > > If I takehttp://www.kandroid.org/android_pdk/build_system.htmlassource > > there are 3 Layers > > > Product (The product layer defines a complete specification of a shipping > > product) > > Device (The device layer represents the physical layer of plastic on the > > device) > > Board (The board layer represents the bare schematics of a product) > > Arch (e.g. armv7) > > >http://source.android.com/porting/build_new_device.htmlsuggest > > creating a directory called "vendor" but if I look a the android platform > > source code changes are found in a directory called "device" for example > > device/htc. Again > > if I look at the code for the emulator and such product definitions are > > found under the build system (e.g. build/target/product). In terms of > > porting to certain hardware I inf also found the "hardware" directory. > > > so for short can somebody tell me what is the role/idea is behind > > build/target/product > > vendor/example/product > > device/example/product > > and hardware/ ? > > > Greetings -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
