Thu Nov 5 01:26:39 CET 2009
do_menuconfig is called just after do_patch, which seems wrong, because
in do_configure_prepend it prepares few lines to .config (like logo,
*abi, thumb) and then appends defconfig without conflicting lines.
If I need to enable some options temporary then I use
-c configure (for sane .config)
-c menuconfig (for temporary modification)
But if you want to use menuconfig for updating defconfig used in OE tree
or default config in kernel (like arch/arm/configs/gta02_defconfig) then
do_configure phase would change some options you didn't want to touch
(as they can be OE specific, ie disabling deprecated sysfs paths for
So 1st case is easily workarounded by user in current state.
2nd will be a bit more difficult if its moved to after do_configure
as you need to revert all changes automagically introduced in
do_configure_prepend in menuconfig or replace .config with defconfig
between do_configure and do_menuconfig or just use load ../defconfig
option from menuconfig. (Hmm doesn't look more difficult now :))
Btw: haven't checked but if you use
-c menuconfig (create custom config)
isn't your custom .config rewritten in do_configure phase with defconfig
+ do_configure_prepend automagic?.
uin:136542059 jid:Martin.Jansa at gmail.com
Jansa Martin sip:jamasip at voip.wengo.fr
More information about the Openembedded-devel