On Tue, 03 Dec 2013 20:21:10 -0500, Weedy wrote:
> NP Trunk just has too much churn for lazy ways of updating to cope.
What I'd been doing (and seemed to work for quite some time) was to do a
make menuconfig before running the build - that seemed to deal with
things like ulibc version changes without too much trouble.
I also pull a package config from my router before the build via ssh and
use that to install/configure packages from various feeds. I'm now
wondering if that's still going to work for me as I rework my process -
or if that's even necessary any more.
My script for building the update follows:
--- snip ---
#!/bin/bash
pushd .
cd /home/jhenderson/Downloads/openwrt
make distclean
cp config.txt .config
svn update
scripts/feeds update
ssh router opkg list-installed > installed-packages.txt
cat installed-packages.txt | awk '{print "scripts/feeds install " $1}' |
sh
cp config.txt .config
make menuconfig
make
cp .config config.txt
popd
--- snip ---
It looks like instead of using my .config from previous builds, I should
set the target up with a file containing my hardware build requirements
and then determine just the packages to install from the non-feed-based
packages (ie, from the stock openwrt svn tree), and then add my installed
packages from feeds after that, and let the built-in dependency
resolution deal with the underlying stuff.
Digging into the busybox/readlink issue, it looks like that configuration
is stored in the subdirectory, and doing a make distclean is /probably/
blowing that configuration away. I don't find any busybox config items
in the main .config file at all.
Seems it's time for a smarter script. :)
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
