Hi @all, I have found a solution to build only one libary and not the whole system:
build/envsetup.sh # run this at top of your android directory choosecombo # here you have to choose your target cd hardware/module # change to the directory of your libary mm # just run this command ;-) This is so nice - just few seconds till the libary is built ! Greetz Andreas Hornsteiner On 24 Nov., 13:50, Dudero <[email protected]> wrote: > Hello Deva, > > thanks for your advise! > > To my last question: > > Yes, I mean how to test a hal implementation on real target - in my > case thegpsstub: "libgps.so" > > Which possibilities do i have? > > Best Regards, > Andreas Hornsteiner > > On 23 Nov., 18:21, Deva R <[email protected]> wrote: > > > > > > > > > >how it is possible to build only one libary and not the whole system? > > > --> like: "make libgps.so" > > > only one library is not possible => all statically linked libraries also > > will be built. > > try "make libgps" (like "make <module-name>") > > > a sample incremental build with stagefright is shown below., > > > >Is it also possible to develope a hal implementation without the > > >complete android build system -> NDK? > > > You can develop a compilable native code with NDK, i guess.. but testing > > specific hardware features (like HAL,gps) should be on appropriate target > > > >And my last question is which possibilities are there to test a new > > >hal implementation? > > > real target? > > > PS. > > /data/l27_8$ touch frameworks/base/media/libstagefright/OMXCodec.cpp > > /data/l27_8$ make libstagefright > > ============================================ > > PLATFORM_VERSION_CODENAME=REL > > PLATFORM_VERSION=2.2.1 > > TARGET_PRODUCT=blaze > > TARGET_BUILD_VARIANT=eng > > TARGET_SIMULATOR= > > TARGET_BUILD_TYPE=release > > TARGET_BUILD_APPS= > > TARGET_ARCH=arm > > HOST_ARCH=x86 > > HOST_OS=linux > > HOST_BUILD_TYPE=release > > BUILD_ID=MASTER > > ============================================ > > target thumb C++: libstagefright <= > > frameworks/base/media/libstagefright/OMXCodec.cpp > > In file included from frameworks/base/include/media/IOMX.h:28, > > from > > frameworks/base/include/media/stagefright/OMXCodec.h:21, > > from frameworks/base/media/libstagefright/OMXCodec.cpp:42: > > dalvik/libnativehelper/include/nativehelper/jni.h:489: note: the mangling of > > 'va_list' has changed in GCC 4.4 > > Install: out/host/linux-x86/bin/apriori > > Install: out/host/linux-x86/bin/soslim > > Install: out/host/linux-x86/bin/icudata > > target Non-prelinked: libicudata-us > > (out/target/product/blaze/symbols/system/lib/libicudata.so) > > target SharedLib: libstagefright > > (out/target/product/blaze/obj/SHARED_LIBRARIES/libstagefright_intermediates > > /LINKED/libstagefright.so) > > target Prelink: libstagefright > > (out/target/product/blaze/symbols/system/lib/libstagefright.so) > > libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned > > long) != 8 > > libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned > > long) != 8 > > libelfcopy: Warning: Location lists in .debug_info section aren't in > > ascending order! > > libelfcopy: Warning: Range lists in .debug_info section aren't in ascending > > order! > > libelfcopy: Warning: Range lists in .debug_ranges section start at 0x48 > > target Strip: libstagefright > > (out/target/product/blaze/obj/lib/libstagefright.so) > > Install: out/target/product/blaze/system/lib/libdl.so > > Install: out/target/product/blaze/system/lib/libc.so > > Install: out/target/product/blaze/system/lib/libstdc++.so > > Install: out/target/product/blaze/system/lib/libm.so > > Install: out/target/product/blaze/system/lib/liblog.so > > Install: out/target/product/blaze/system/lib/libcutils.so > > Install: out/target/product/blaze/system/lib/libz.so > > Install: out/target/product/blaze/system/lib/libutils.so > > Install: out/target/product/blaze/system/lib/libbinder.so > > Install: out/target/product/blaze/system/lib/libEGL.so > > Install: out/target/product/blaze/system/lib/libwpa_client.so > > Install: out/target/product/blaze/system/lib/libnetutils.so > > Install: out/target/product/blaze/system/lib/libhardware_legacy.so > > Install: out/target/product/blaze/system/lib/libpixelflinger.so > > Install: out/target/product/blaze/system/lib/libhardware.so > > Install: out/target/product/blaze/system/lib/libui.so > > Install: out/target/product/blaze/system/lib/libsonivox.so > > Install: out/target/product/blaze/system/lib/libicudata.so > > Install: out/target/product/blaze/system/lib/libicuuc.so > > Install: out/target/product/blaze/system/lib/libexpat.so > > Install: out/target/product/blaze/system/lib/libsurfaceflinger_client.so > > Install: out/target/product/blaze/system/lib/libcamera_client.so > > Install: out/target/product/blaze/system/lib/libmedia.so > > Install: out/target/product/blaze/system/lib/libvorbisidec.so > > Install: out/target/product/blaze/system/lib/libstagefright_amrnb_common.so > > Install: out/target/product/blaze/system/lib/libstagefright_avc_common.so > > Install: > > out/target/product/blaze/system/lib/libstagefright_color_conversion.so > > Install: out/target/product/blaze/system/lib/libstagefright.so > > /data/l27_8$ > > > On Tue, Nov 23, 2010 at 3:59 PM, Dudero <[email protected]> wrote: > > > Hello, > > > > how it is possible to build only one libary and not the whole system? > > > > --> like: "make libgps.so" > > > > Is it also possible to develope a hal implementation without the > > > complete android build system -> NDK? > > > > And my last question is which possibilities are there to test a new > > > hal implementation? > > > > Best Regards, > > > Andreas Hornsteiner > > > > -- > > > unsubscribe: > > > [email protected]<android-porting%2Bunsubscribe@ > > > googlegroups.com> > > > website:http://groups.google.com/group/android-porting > > > -- > > Regards, > > Devawww.bittoggler.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
