I think it does, because that also saves a lot of questions in the future (hopefully). Because I think a lot of people that build there own custom openwrt firmware often also modify the busybox config.
2013/12/17 Yousong Zhou <[email protected]>: > On 17 December 2013 22:13, [email protected] > <[email protected]> wrote: >> Hi yousong, >> >> Can you give a example how to call menuconfig for busybox ? > > I am doing menuconfig for busybox in OpenWrt build environment in > which busybox tarball has already been extracted. Your situation may > vary. Busybox itself provide menuconfig just like those for > OpenWrt/Buildroot/Kernel. > > $ make -C build_dir/target-mips_34kc_uClibc-0.9.33.2/busybox-1.19.4/ > menuconfig > > Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"? > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
