I have a build script which patches the .mk file for the target system 
to add (and remove) some packages, and puts a .config file in the
openwrt/trunk directory.  It then runs make defconfig, and this used to 
cause removed packages not to be built, and the added ones to be
built.

But I have just re-run it and none of the extra packages I requested
seem to have been built.  Has something changed with the processing
of make defconfig?  Do I now have to change the .config file as well
to include the packages?

Essentially what I want to be able to do is to take a standard profile
(say the Pcengines one for wrap boards) and add some extra packages
that I always need, remove the ones I do not need, and make a few 
changes to the .config.  And this method of patching the .mk (I unpatch
it when I finish) and creating a short .config seemed to work, but it now
seems to be unstable.

I need to have a common application profile across a number of platforms
(wrap, rb1xx etc) and this seemed the best way to achieve it - other 
suggestions greatfully received.

David
_______________________________________________
openwrt-users mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to