Hi Thomas,
Yes, CONFIG_TARGET=env solves my problem from trunk.
Thanks for pointing out this usage. Probably documentation would also help
on CONFIG_TARGET usage.
Btw, i got error while i did "make CONFIG_TARGET=env kernel_menuconfig"
since there was no $(TOPDIR)/env already present. Perhaps the following
change would help not throw up the error?:
Index: include/target.mk
===================================================================
--- include/target.mk (revision 31785)
+++ include/target.mk (working copy)
@@ -144,6 +144,7 @@
ifeq ($(CONFIG_TARGET),env)
LINUX_RECONFIG_LIST = $(LINUX_KCONFIG_LIST)
LINUX_RECONFIG_TARGET = $(TOPDIR)/env/kernel-config
+ $(shell mkdir -p $(TOPDIR)/env)
endif
__linux_confcmd = $(SCRIPT_DIR)/kconfig.pl $(2) $(patsubst %,+,$(wordlist
2,9999,$(1))) $(1)
Regards
Kalyan
On Sun, May 20, 2012 at 8:24 PM, Thomas Langer <thomas.lan...@gmx.net>wrote:
> Hi Kalyan,
>
> with your change it is not possible anymore for a developer to use this
> command for editing the configuration of a target or subtarget.
> But this is the main functionality behind this.
>
> Have you had a look at the existing option to do "make kernel_menuconfig
> CONFIG_TARGET={platform,subtarget,env}"?
> You removed this feature by not using LINUX_RECONFIG_TARGET anymore.
> Maybe your problem would already be solved by making "CONFIG_TARGET=env"
> the default?
>
> If you differentiate between "users" and "developers", the question is,
> why a "user" has to do "make kernel_menuconfig" at all.
> For me it looks like these options should be provided by the normal "make
> menuconfig" instead.
>
> Best regards,
> Thomas
>
> Am 20.05.2012 15:15, schrieb kalyan:
>
> Hi All,
> The current implementation of the build system for handling "make
> kernel_menuconfig" involves modifying the default configurations under
> target/linux/.
>
> A side affect of this process is that the default configuration under
> target/linux is now lost.While within the version control system it is
> possible to recover the default configuration, there is no way to recover
> it outside version control system. The only fall back is to refer to
> originally shipped openwrt tar ball/SDK agin.
>
> The attached patch attempts to tackle this problem. The patch creates
> .config.user under kernel build directory for changes done through "make
> kernel_menuconfig".If the developer wants to go back to default
> configuration, "make kernel_defconfig" is sufficient. If the developer is
> interested in viewing his/her changes,"make kernel_user" can show them.
>
> The above solution does not touch the default configurations under
> target/linux while still achieving original build system goal of providing
> flexibility to developer to change kernel configuration.
>
> I would like to get feedback on the patch and wether such enhancement
> can make its way to trunk.
>
> Thanks and Regards
> Kalyan
>
>
> _______________________________________________
> openwrt-devel mailing
> listopenwrt-devel@lists.openwrt.orghttps://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
