OpenWrt Forum Archive

Topic: Buildroot questions

The content of this topic has been archived on 24 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I'm a beginner at this so please go easy on me...

After running "make menuconfig" where is the list of packages to be included stored?  I noticed every package got downloaded and built, even ones I did not select in "make menuconfig".  ImageBuilder uses the files under target/linux/imagebuilder/lists but I do not want to use ImageBuilder.  Does a completely custom build use another file somewhere?  I want to build firmware without dhcp.  Later I want to include dnsmasq and after that I might want to try another dns package.  Is there a file that I can easily modify to pick up these package changes when I do a custom build?  If I re-run "make menuconfig" and de-select dnsmasq would that be enough?  FWIW I do not like "make menuconfig".  Never have, even for just building regular Linux kernels.  I find it confusing.  That doesn't mean I won't use it when necessary. smile

After running "make" I see .bin files for openwrt-wa840g, we800g, wr850g, wrt54g, wrt54gs, wrt54g3g, wrt54gs_v4 and wrtsl54gs.  Squashfs and jffs2.  I am only interested in building a squashfs flavor firmware for the wrt54gs.  Is there a makefile target or config file somewhere that will turn off generation of all the other binaries?

Dropbear.  I will always have dropbear.  Always.  What is the best way to preserve dropbear_rsa_host_key, dropbear_dsa_host_key and the public keys for my other boxes, authorized_keys on the target filesystem?  The /etc/dropbear directory is not in the skeleton fs at packages/base-files/default.  Can I just add a dropbear subdir there, put the files in it and have them get picked up for ever more?

Thanks in advance.

(Last edited by Craven on 12 Mar 2006, 03:07)

Well, I answered one of my own questions re. the dropbear authorized_keys file.  Yes, that works if I add it to package/base-files/default/etc/dropbear and rebuild.  It becomes "sticky" there and is automatically on the router after the new firmware is loaded.

I also verified FWIW that re-flash via the webif works over a wireless connection.  Not a recommended procedure but it works.  I got lazy after a few hard-wired boot_wait tftp upgrades.

Hi

Does anyone know how to select which packages kamikaze creates during a make?

On more recent versions, menuconfig offers an option to create only squashfs or jffs2 but I would like to _only_ create the openwrt-brcm-2.6-squashfs.trx and not bother creating the device-specific .bin files.


any ideas?

Thanks

john

The discussion might have continued from here.