Hi David, Think you for your answer.
I'm sorry for my copy&paste mistake. I can compile with TARGET_SIMULATOR=true without any problem. but when set "TARGET_SIMULATOR=false" in compile command, error below happend make: *** No rule to make target `out/host/linux-x86/bin/emulator', needed by `out/host/linux-x86/bin/dexpreopt.py'. Stop. Then I want to compile the bionic first.I did as follow. 1. Modify the Android.mk in mydroid/bionic to compile bionic in simulator target 2. Compile all again with TARGET_SIMULATOR=true the output as follow: -------------------output------------------------ target thumb C: linker <= bionic/linker/linker.c target thumb C: linker <= bionic/linker/dlfcn.c bionic/linker/linker.c:15:25: error: sys/atomics.h: No such file or directory bionic/linker/linker.c:16:21: error: sys/tls.h: No such file or directory In file included from bionic/linker/dlfcn.c:18: bionic/linker/linker.h:20: error: expected specifier-qualifier-list before 'uintptr_t' In file included from bionic/linker/linker.c:18: bionic/linker/linker.h:20: error: expected specifier-qualifier-list before 'uintptr_t' bionic/linker/linker.h:50: error: expected specifier-qualifier-list before 'uintptr_t' bionic/linker/linker.h:50: error: expected specifier-qualifier-list before 'uintptr_t' ---------------copy end(firest several lines)------------------ How can I compile bionic and other modules(init etc.)?? On 11月14日, 下午7时24分, "David Turner" <[EMAIL PROTECTED]> wrote: > Do not use TARGET_SIMULATOR=true, this flag should only be set when building > the Android simulator, > which doesn't require all system libraries and runs the Android "system" > into a single process on the host > machine. > > that's why you have problems when building certain libraries (e.g. the > simulator uses the host's C library, not Bionic) > > the x86 port only uses Android's own software OpenGL renderer. There is no > support for hardware-accelerated graphics > yet (and it's not like there is any kind of standard API for that on Linux). > OpenCore is supposed to be portable, so I > assume it runs (but I may be mistaken) > > you can't easily replace OpenCore with something else, unless you modify all > the framework code that depends on it. > (this has never been tested internally) > > On Fri, Nov 14, 2008 at 2:52 AM, Gang lee <[EMAIL PROTECTED]> wrote: > > > Hi all: > > > Although I can compile with the command line: > > make -j2 TARGET_ARCH=x86 TARGET_PRODUCT=generic > > TARGET_SIMULATOR=true TARGET_BUILD_TYPE=release TARGET_OS=linux > > LOCAL_PRELINK_MODULE=false > > > but I found lot of modules cannot be compiled with > > "TARGET_SIMULATOR=true", if set false,the bionic(libc) met some files > > (.h files) missing and compile failed. > > Has anyone compiled the bionic successful? > > > Another question, Does any one knows more detail information about the > > official x86 porting? for example: > > Does the x86 porting support OpenGL? > > Does the x86 porting still use openCore as the Media Framework? and > > the openCore can be replaced by others(just like Hilex or GStreamer)? --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
