Hi Benno, I think you should really consider creating a branch for this purpose. There is very little chance that any other technique is going to end up very not nasty at that point. Better create your own branch, and do whatever crazy things you want to do there
Also keep in mind that there are also quite a few Linux specific stuff in the pthread implementation, signal handling, syscall stubs generation and quite a few more places. I don't think it's going to be very easy. Good luck though On Sat, Dec 20, 2008 at 5:20 AM, Ben Leslie <[email protected]> wrote: > > Hi all, > > I'm looking at porting Android to a non-Linux kernel. It makes sense > for me to re-use the existing bionic C library, however currently > parts are quite Linux specific. In particular the > bionic/libc/include/sys directory is pretty much Linux specific. > > I'm trying to work out the best way to structure things to provide an > alternative sys directory for my non-Linux kernel. A horrible way > would be to put ifdefs through-out the existing headers. A better way > would be to have something like bionic/libc/include/sys-<$kernel>, but > then the problem is fixing the references to "sys/". Options could be: > symlink, nasty preprocessor macro or copy header files into the /out > directory and include from there. > > Does anyone on the platform team have suggestions about the best way to go? > > Cheers, > > Benno > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
