Changelog since 2013-10-13 until 2013-10-20. Projects included in this report:
bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom:
Hi!
What configuration kernel build really uses - .config or defconfig?
It seems, that menuconfig (bitbake -c menuconfig ) use always .config file.
I have problem that changes in defconfig are not seen in kernel features.
Instead they seem the same that are in .config file
I have tried
The defconfig file is present in the meta-layers and copied to the kernel
build directory.
It is used to create the .config file in the kernel source directory.
If you modify the .config file, you will see changes in the kernel file.
if you modify the defconfig file in the build directory,
Thanks Ulf,
It seems to work in that way. However, I'm a bit surprised that it works so
as as I mentioned above all the procedures -
patching defconfig in the kernel build directory, providing defconfig in
metadata and providing configuration fragments as described in the Yocto
Kernel development
On 2013-10-22 17:20, matti kaasinen wrote:
Thanks Ulf,
It seems to work in that way. However, I'm a bit surprised that it works so
as as I mentioned above all the procedures -
patching defconfig in the kernel build directory, providing defconfig in
metadata and providing configuration fragments
On 2013-10-18 10:36, Koen Kooi wrote:
Op 18 okt. 2013, om 09:27 heeft Ulf Samuelsson angstrom-...@emagii.com het
volgende geschreven:
I have built the cloud9-gnome-image configured for beaglebone
using the master branch of Angstrom and loaded it on a Beaglebone Black.
The Beaglebone Black has
