93e4f2d5ed
4 out of 5 packages who are not using autotools but needed their gnuconfig files updated were not complying with the recommandation in support/gnuconfig/README.buildroot. The fifth package was converted to be like the others: use UPDATE_CONFIG_HOOK as a <pkg>_POST_PATCH_HOOKS rather than calling the CONFIG_UPDATE macro directly. Now that all packages are consistent, update the README.buildroot file to match the reality. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
28 lines
1019 B
Plaintext
28 lines
1019 B
Plaintext
--- HOWTO ---
|
|
If your package uses config.guess and/or config.sub, then it probably
|
|
relies on the autotools as its build system. In this case, you should
|
|
use the autotools-package infrastructure, which will take care of updating
|
|
the config.guess and/or config.sub files appropriately. See the
|
|
Buildroot documentation for details about the autotools-package
|
|
infrastructure.
|
|
|
|
If for some reason your package does not use the autotools-package
|
|
infrastructure, you can request the config.guess and/or config.sub
|
|
files of your package to be updated by using:
|
|
|
|
<pkg>_POST_PATCH_HOOKS += UPDATE_CONFIG_HOOK
|
|
|
|
--- UPDATE ---
|
|
GNU config is now managed in git, so to update:
|
|
|
|
# git clone git://git.savannah.gnu.org/config.git
|
|
# cp config/config.* .
|
|
# for p in $(ls patches/*.patch); do patch -p1 < $p; done
|
|
# rm -rf config
|
|
|
|
Currently no patches are needed, but they may be needed again in the
|
|
future.
|
|
|
|
The current Buildroot version is based on the Git commit
|
|
dafd8e767ec87b90aac62f0fcedd11944c84b50a of the config.git repository.
|