Android work in progress

[Hin-Tak Leung]

--- On Sun, 11/9/11, Tanguy Pruvot <tanguy.pruvot at gmail.com> wrote:

> Please  re-read  my first
> phrase... "I suggest you check the currently
> used configs"
> 
> And for your information, the last commit in 1.20 was one
> of them.
> 
> I dont like your "aggro", why do you react like that ?

WTF. If you have a different config that's more useful than the current one on busybox's git, then send a patch to the mailing list. I am not interested in forks, and I have no intention of of rooting my android device - at least not until the warranty expires, which isn't for another whole year; so I have very little intention of checking out anything that's overly cyanogenmod-specific, or any processes that roots a device or any software that requires a rooted device. Am I clear enough? I am still not getting what's your intention of e-mailing over and over and not explaining what you are trying to say clearly.

> > --- On Sun, 11/9/11, Tanguy Pruvot <tanguy.pruvot at gmail.com>
> wrote:
> 
> >> The difference between CyanogenMod
> >> and AOSP is that busybox is used
> >> as default for adb shell.
> >> 
> >> CyanogenMod  doesnt  require  a custom
> >> kernel, it is possible also for
> >> some devices, but there is nothing related to
> kernel. As i
> >> said it is
> >> a selection of applets which works on android and
> doesn't
> >> conflict with
> >> "toolbox", a kind of mini busybox used on all
> android
> >> devices.
> >> 
> >> But you can continue to ignore us and make your
> custom
> >> selection of applets...
> >> 
> >> Also, android shell is unicode, all devices can
> switch on
> >> the fly
> >> default  language  to  Russian 
> >> or  Chinese  chars and need to support
> >> listing   all  these  wide 
> >> chars.  There  is  no "localized" versions
> >> (except for Arabic which is more an extension of
> >> translations)
> 
> > I really am not comprehending what you are trying to
> say, and I am
> > not sure what's this "continue to ignore us" all about
> - forking
> > somebody else's work is rarely a good option. If
> that's what you
> > said - I quite routinely ignore forks and people
> "doing their own things".
> 
> > I just like busybox to work on my unmod'ed and
> unrooted android
> > device - so any matter and topic specific to
> cyganogenmod is irrelevant.
> 
> > If any of the tools/whatever you mentions works on
> unmod'ed and
> > unrooted devices, fair enough; and my opinion is still
> that any
> > enhancements should be sent upstream - I really do not
> need to hear
> > how good cyanogenmod is (if that's what you are trying
> to say), as
> > that's quite irrelevant. I really do not need to hear
> how good
> > cyanogenod is, as I do not intend to root my android
> device any time
> > soon. Please stop advertising for cyanogenmod if
> that's what you are trying to do.
> 
> >> > --- On Sun, 11/9/11, Tanguy Pruvot <tanguy.pruvot at gmail.com>
> >> 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
> <vda.linux at googlemail.com>
> >> >> 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
> >> >> > busybox at busybox.net
> >> >> > http://lists.busybox.net/mailman/listinfo/busybox
> >> >> 
> >> >>
> >> 
> >>
> 
>