Can anybody say where is the source code for that GNU Parted 1.8.8.1.179-aef3 binary? I gave a shot in GitHub but seems it is a blob, meaning that some company didn't release the source code? It claims to be under the GPL.
I'm compiling a custom gcc including the D language on android itself. I have C4Droid gcc binaries installed as well as Debian Wheezy on chroot with gcc/g++ 4.6. I was thinking I could change the host mode to arm-linux-androideabi in configure? Does the NDK build-gcc.sh script call the NDK toolchain to compile or the host systems gcc? Would this be enough to get the source to compile a android runnable binary? Thanks in advanced.
Hi! I'm writing desktop software which is using aapt (Android Asset Packaging Tool). The question is: what license does aapt use? I'd like to deploy it with my software (which licensed under GNU GPL v2) but I couldn't find any information about aapt licensing. Thank you.
For build a kernel compatible with my device, what do I need ? module list (took from /sys/module) ? only or what else ?
Can I simple use device/generic/common/ source and then configure with module list from /sys/module?
see this and thank me if i helped.
hotvic said:
For build a kernel compatible with my device, what do I need ? module list (took from /sys/module) ? only or what else ?
Can I simple use device/generic/common/ source and then configure with module list from /sys/module?
Click to expand...
Click to collapse
You will want to look at the git log for the kernel binary
in the device project that you are interested in.
Device projects are of the form device/<vendor>/
<name>.
$ git clone https : //android.googlesource.com/device/ti/panda
$ cd panda
$ git log -- max - count= 1 kernel
The commit message for the kernel binary contains a
partial git log of the kernel sources that were used to
build the binary in question. The first entry in the log is
the most recent, i.e. the one used to build that kernel.
You will need it at a later step.
Identifying kernel version
To determine the kernel version used in a particular
system image, run the following command against the
kernel file:
$ dd if= kernel bs =1 skip = $ (LC_ALL = C grep - a -b - o $ '\x1f\x8b\x08\x00\x00\x00\x00\x00' k
For Nexus 5 (hammerhead), this can be accomplished
with:
$ bzgrep - a 'Linux version' vmlinux . bz2
Downloading sources
Depending on which kernel you want,
$ git clone https : //android.googlesource.com/kernel/common.git
$ git clone https : //android.googlesource.com/kernel/exynos.git
$ git clone https : //android.googlesource.com/kernel/goldfish.git
$ git clone https : //android.googlesource.com/kernel/msm.git
$ git clone https : //android.googlesource.com/kernel/omap.git
$ git clone https : //android.googlesource.com/kernel/samsung.git
$ git clone https : //android.googlesource.com/kernel/tegra.git
The goldfish project contains the kernel sources for
the emulated platforms.
The msm project has the sources for ADP1, ADP2,
Nexus One, Nexus 4, and can be used as a starting
point for work on Qualcomm MSM chipsets.
The omap project is used for PandaBoard and Galaxy
Nexus, and can be used as a starting point for work on
TI OMAP chipsets.
The samsung project is used for Nexus S, and can be
used as a starting point for work on Samsung
Hummingbird chipsets.
The tegra project is for Xoom and Nexus 7, and can
be used as a starting point for work on NVIDIA Tegra
chipsets.
The exynos project has the kernel sources for Nexus
10, and can be used as a starting point for work on
Samsung Exynos chipsets.
Downloading a prebuilt gcc
Ensure that the prebuilt toolchain is in your path.
$ export PATH = $ (pwd )/ prebuilts /gcc / linux - x86/ arm / arm -eabi- 4.6 /bin : $PATH
or
$ export PATH = $ (pwd )/ prebuilts /gcc / darwin- x86 /arm / arm - eabi-4.6 / bin: $PATH
On a linux host, if you don't have an Android source
tree, you can download the prebuilt toolchain from:
$ git clone https : //android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-ea
Building
As an example, we would build the panda kernel using
the following commands:
$ export ARCH = arm
$ export SUBARCH = arm
$ export CROSS_COMPILE = arm - eabi-
$ cd omap
$ git checkout <commit_from_first_step>
$ make panda_defconfig
$ make
To build the tuna kernel, you may run the previous
commands replacing all instances of "panda" with
"tuna".
The kernel binary is output as: `arch/arm/boot/zImage`
It can be copied into the Android source tree in order
to build the matching boot image.
Or you can include the TARGET_PREBUILT_KERNEL
variable while using make bootimage or any other
make command line that builds a boot image.
$ export TARGET_PREBUILT_KERNEL =$your_kernel_path / arch/arm / boot/ zImage
That variable is supported by all devices as it is set up
via device/common/populate-new-device.sh
@SidDev said:
You will want to look at the git log for the kernel binary
in the device project that you are interested in.
Device projects are of the form device/<vendor>/
<name>.
$ git clone https : //android.googlesource.com/device/ti/panda
$ cd panda
$ git log -- max - count= 1 kernel
The commit message for the kernel binary contains a
partial git log of the kernel sources that were used to
build the binary in question. The first entry in the log is
the most recent, i.e. the one used to build that kernel.
You will need it at a later step.
Identifying kernel version
To determine the kernel version used in a particular
system image, run the following command against the
kernel file:
$ dd if= kernel bs =1 skip = $ (LC_ALL = C grep - a -b - o $ '\x1f\x8b\x08\x00\x00\x00\x00\x00' k
For Nexus 5 (hammerhead), this can be accomplished
with:
$ bzgrep - a 'Linux version' vmlinux . bz2
Downloading sources
Depending on which kernel you want,
$ git clone https : //android.googlesource.com/kernel/common.git
$ git clone https : //android.googlesource.com/kernel/exynos.git
$ git clone https : //android.googlesource.com/kernel/goldfish.git
$ git clone https : //android.googlesource.com/kernel/msm.git
$ git clone https : //android.googlesource.com/kernel/omap.git
$ git clone https : //android.googlesource.com/kernel/samsung.git
$ git clone https : //android.googlesource.com/kernel/tegra.git
The goldfish project contains the kernel sources for
the emulated platforms.
The msm project has the sources for ADP1, ADP2,
Nexus One, Nexus 4, and can be used as a starting
point for work on Qualcomm MSM chipsets.
The omap project is used for PandaBoard and Galaxy
Nexus, and can be used as a starting point for work on
TI OMAP chipsets.
The samsung project is used for Nexus S, and can be
used as a starting point for work on Samsung
Hummingbird chipsets.
The tegra project is for Xoom and Nexus 7, and can
be used as a starting point for work on NVIDIA Tegra
chipsets.
The exynos project has the kernel sources for Nexus
10, and can be used as a starting point for work on
Samsung Exynos chipsets.
Downloading a prebuilt gcc
Ensure that the prebuilt toolchain is in your path.
$ export PATH = $ (pwd )/ prebuilts /gcc / linux - x86/ arm / arm -eabi- 4.6 /bin : $PATH
or
$ export PATH = $ (pwd )/ prebuilts /gcc / darwin- x86 /arm / arm - eabi-4.6 / bin: $PATH
On a linux host, if you don't have an Android source
tree, you can download the prebuilt toolchain from:
$ git clone https : //android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-ea
Building
As an example, we would build the panda kernel using
the following commands:
$ export ARCH = arm
$ export SUBARCH = arm
$ export CROSS_COMPILE = arm - eabi-
$ cd omap
$ git checkout <commit_from_first_step>
$ make panda_defconfig
$ make
To build the tuna kernel, you may run the previous
commands replacing all instances of "panda" with
"tuna".
The kernel binary is output as: `arch/arm/boot/zImage`
It can be copied into the Android source tree in order
to build the matching boot image.
Or you can include the TARGET_PREBUILT_KERNEL
variable while using make bootimage or any other
make command line that builds a boot image.
$ export TARGET_PREBUILT_KERNEL =$your_kernel_path / arch/arm / boot/ zImage
That variable is supported by all devices as it is set up
via device/common/populate-new-device.sh
Click to expand...
Click to collapse
but... I want a general way of build the kernel, i.e not using the device-specific code.
My idea is build most recent kernel to devices w/o updates in source tree.
and the device in my mind is a Alcatel One Touch POP C3, which there's no device/alcatel ...
Thank you.
hotvic said:
but... I want a general way of build the kernel, i.e not using the device-specific code.
My idea is build most recent kernel to devices w/o updates in source tree.
and the device in my mind is a Alcatel One Touch POP C3, which there's no device/alcatel ...
Thank you.
Click to expand...
Click to collapse
You will need device specific code to get you started, I would recommend checking out this section on source forge where Alcatel keeps it's open source files that include the kernel source for most all there devices by searching for your device model. Let me know if you still have questions.
hotvic said:
but... I want a general way of build the kernel, i.e not using the device-specific code.
My idea is build most recent kernel to devices w/o updates in source tree.
and the device in my mind is a Alcatel One Touch POP C3, which there's no device/alcatel ...
Thank you.
Click to expand...
Click to collapse
kernel is general made device specific
shimp208 said:
You will need device specific code to get you started, I would recommend checking out this section on source forge where Alcatel keeps it's open source files that include the kernel source for most all there devices by searching for your device model. Let me know if you still have questions.
Click to expand...
Click to collapse
Ok, I've got 4033E code and kernel source is inside it.
@SidDev said:
kernel is general made device specific
Click to expand...
Click to collapse
is there a general kernel where I can merge the alcatel's source and most recent source ?
hotvic said:
Ok, I've got 4033E code and kernel source is inside it.
is there a general kernel where I can merge the alcatel's source and most recent source ?
Click to expand...
Click to collapse
You can now use that kernel source to build the defconfig for your device which is usually listed under arch/arm/configs your devicecodename_defconfig. If the sources don't include any compile instructions or a README let me know and I can help if you get stuck. While you could take the latest version of the Android kernel for say the Nexus 5, and merge the Alcatel sources there are a lot of merge problems that would have to be fixed as well as other compile errors that would result, best to stay away from this until you really know what your doing and feel more comfortable with all the things involved.
I am new to android source code development. I am using Ubuntu 14.04. I used official web "source.android" as a guideline for setting up and downloading source code.
Installed:
1) Python 2.7.10
2) GNU Make 3.82
3) Git latest
4) OpenJDK: sudo apt-get install openjdk-6-jdk
Downloaded following source code:
Build Number: JDQ39, android-4.2.2_r1, Jelly Bean, Galaxy Nexus, Nexus 7, Nexus 4, Nexus 10
It downloaded approximately 65GB, is it fine?
In guide line provided on source.android.com:
a) HADN'T USED SEPARATE OUTPUT DIRECTORY.
b) HADN'T OPTIMIZED A BUILD ENVIRONMENT
c) WASN'T ABLE TO CONFIGURE: USING AUTHENTICATION
d) AFTER EDITING CODE DON'T KNOW HOW TO VERIFY GIT TAG
When I type command "lunch aosp_arm-eng" after ". build/envsetup.sh" it says:
"build/core/product_config.mk:223: *** Cannot locate config makefile for product "aosp_arm". Stop.
** Don't have a product spec for: 'aosp_arm'
** Do you have the right repo manifest?"
I have tried instruction sets from various forums but hadn't found any solution. Kindly guide me how to solve this error while building source code.