On 12/01/13 19:30, darius wrote: > Thanks for replying. So why do we need 'make kernel_menuconfig'? Is it > only for configuring kernel option which later must be compiled not with > 'make'? How then externally build kernel will be included into firmware's > 'bin' file? I'm really lost. Please could you guide me a little bit more? > I'd like to include some features into kernell statically. Or maybe it is > easier to do it as module?
I haven't actually done this but according to the wiki page below you can do a "make kernel_menuconfig" after a "make menuconfig" but before doing the final make and that should include your kernel changes. Not that the description below is explicit but it's implied by the context surrounding the below section on the wiki... or that's how it seems to me anyway. http://wiki.openwrt.org/doc/howto/build Kernel configuration While you won't typically need to do this, you can do it: make kernel_menuconfig Note that make kernel_menuconfig modifies the Kernel configuration templates of the build tree, clearing the build_dir will not revert them. The changes can be reviewed with svn diff target/linux/ and reverted with svn revert -R target/linux/. See: Customizing the kernel options _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
