--- On Sun, 11/9/11, Tanguy Pruvot <[email protected]> wrote: > Bonjour, > > I suggest you check the currently used configs in > Cyanogen AOSP variant: > > https://github.com/CyanogenMod/android_external_busybox > > check file .config-full which is > the actual profile we use for 500000 > devices. "only" 30000 use the 1.19.x branch since a > few months. > > .config-minimal is used as > a static "library" to build recovery > executable (it is a busybox extended with ext4 > library and other stuff) > > when i see default paths set to "/var" i see > directly there is a problem > > arm-linux-androideabi- is a standalone > ndk compiler but the one in > android repo toolchain is > prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc > > or 4.4.0 in old froyo
I am not sure what's the point of your message - the whole idea of what I did was that ndk is both commonly available to developers of the android platform, and also "official", and does not require a separate compiler download from say, codesourcery or build one's own compiler/bionic. So the question is 1. does the cyanogenmod work requires a compiler that not from the ndk and/or a libc which is not bionic, or a kernel that is not stock? 2. does it depends on the rest of any cyanogenmod-specific bits and pieces? If either of these is true, the work is of no use and irrelevant in the current context - I heard and read that cyanogenmod does good work - but many of us don't and would rather not root our devices: there is the voiding of warranty for one reason. 3. If the cyanomodgen busybox work has any interesting functionality which is not in upstream stock busybox, these extra functionality should ideally be sent back and incoporated. (with some extra config option, etc if they cannot be built with standard ndk compiler). > > --- On Fri, 9/9/11, Denys Vlasenko <[email protected]> > wrote: > > >> Thanks for your work! > >> > >> I incorporated your fixes in this commit: > >> > >> http://git.busybox.net/busybox/commit/?id=e0894f567ad379f554300886ae3adf087be1efa2 > >> > >> Does simple > >> > >> make android2_defconfig && make > >> > >> in current git tree work? > > > Yes, works beautifully. Got current head > > (7b46d11582047d0dd21b547ff4a913defe646d40) . Still a > fair number of > > warnings. I really think doing it with the android > ndk-derived > > standalone toolchain is more convenient. > > > Thanks a lot > > Hin-Tak > > _______________________________________________ > > busybox mailing list > > [email protected] > > http://lists.busybox.net/mailman/listinfo/busybox > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
