Someone else said that full support will come with kernel 3.5. But does that mean Linux apps will be able to work on Android then?
Linux apps generally expect a full software stack. Android's userspace is radically different (and for good reason). There's no GNU libc or GNU coreutils or GTK/Qt or X. There's a minimal libc implementation, busybox, and an Android-specific framebuffer-based GUI framework. From the source it appears that Google have tried hard to exclude GPL'd code as much as possible, too. Getting Linux apps to (natively) run on An…
Android is almost fully supported with Linux kernel 3.3
11–18 of 18 posts
Re: Android is almost fully supported with Linux kernel 3.3
#12Don't be too hopeful- Binder is still a big sticking point, and nothing is going to work without it. The two schools of thought on it are: * It is a terrible, terrible interface that doesn't belong in the kernel * Linux supports SysV IPC because other Unices do, Binder is at least as popular Before you pile in and declare your reasonableness by endorsing the latter position, please understand that the former is not e…
Re: Android is almost fully supported with Linux kernel 3.3
#13Someone else said that full support will come with kernel 3.5. But does that mean Linux apps will be able to work on Android then?
Re: Android is almost fully supported with Linux kernel 3.3
#14Earlier quoted context omitted.
Linux apps generally expect a full software stack. Android's userspace is radically different (and for good reason). There's no GNU libc or GNU coreutils or GTK/Qt or X. There's a minimal libc implementation, busybox, and an Android-specific framebuffer-based GUI framework. From the source it appears that Google have tried hard to exclude GPL'd code as much as possible, too. Getting Linux apps to (natively) run on An…
No busybox in android; that too is GPL software that Andy Rubin and the pre-Google Android people didn't want to ship. They actually hacked up a minimal "toolbox" to avoid shipping it. Sad, really.
Re: Android is almost fully supported with Linux kernel 3.3
#15Don't be too hopeful- Binder is still a big sticking point, and nothing is going to work without it. The two schools of thought on it are: * It is a terrible, terrible interface that doesn't belong in the kernel * Linux supports SysV IPC because other Unices do, Binder is at least as popular Before you pile in and declare your reasonableness by endorsing the latter position, please understand that the former is not e…
Binder was merged. But yes, both of the above are true.
Re: Android is almost fully supported with Linux kernel 3.3
#16Earlier quoted context omitted.
Linux apps generally expect a full software stack. Android's userspace is radically different (and for good reason). There's no GNU libc or GNU coreutils or GTK/Qt or X. There's a minimal libc implementation, busybox, and an Android-specific framebuffer-based GUI framework. From the source it appears that Google have tried hard to exclude GPL'd code as much as possible, too. Getting Linux apps to (natively) run on An…
No busybox in android; that too is GPL software that Andy Rubin and the pre-Google Android people didn't want to ship. They actually hacked up a minimal "toolbox" to avoid shipping it. Sad, really.
Re: Android is almost fully supported with Linux kernel 3.3
#17Someone else said that full support will come with kernel 3.5. But does that mean Linux apps will be able to work on Android then?
You can recompile most Linux apps to work on an Android phone now. Anything requiring graphics will require a complete rework, though, because Android doesn't have X.
Re: Android is almost fully supported with Linux kernel 3.3
#18Earlier quoted context omitted.
No busybox in android; that too is GPL software that Andy Rubin and the pre-Google Android people didn't want to ship. They actually hacked up a minimal "toolbox" to avoid shipping it. Sad, really.
Why did they remove it? What is GPL stopping them from doing?