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 list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to