3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-23 10:15:57 +01:00
Code Issues Releases Wiki Activity

configure: make it work from clean repo

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2018-09-23 14:26:53 +01:00
parent 74b51fc044
commit c0b60d6b4c
3 changed files with 41 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
README.adoc
View File

@@ -8571,7 +8571,7 @@ parsecmgmt -a run -p splash2x.fmm -i test
====== PARSEC uninstall
If you want to remove PARSEC later, Buildroot doesn't provide an automated package removal mechanism as documented at: link:https://github.com/buildroot/buildroot/blob/2017.08/docs/manual/rebuilding-packages.txt#L90[], but the following procedure should be satisfactory:
If you want to remove PARSEC later, Buildroot doesn't provide an automated package removal mechanism: <<remove-buildroot-packages>>, but the following procedure should be satisfactory:
....
rm -rf \
@@ -9575,6 +9575,14 @@ For how to use that package, see: <<packages-directory>>.
Then iterate trying to do what you want and reading the manual until it works: https://buildroot.org/downloads/manual/manual.html
=== Remove Buildroot packages
Once you've built a package in to the image, there is no easy way to remove it.
Documented at: link:https://github.com/buildroot/buildroot/blob/2017.08/docs/manual/rebuilding-packages.txt#L90[]
See this for a sample manual workaround: <<parsec-uninstall>>.
=== BR2_TARGET_ROOTFS_EXT2_SIZE
When adding new large package to the Buildroot root filesystem, it may fail with the message:
@@ -10944,23 +10952,30 @@ This can be used to check the determinism of:
==== Release
This is not yet super stable, but one day maybe this script will automatically do a release:
Create a release:
....
git clone https://github.com/cirosantilli/linux-kernel-module-cheat linux-kernel-module-cheat-release
cd linux-kernel-module-cheat-release
./release
....
Source: link:release[].
When ready, that script should:
This scripts does:
* configure
* build
* test
* package with <<release-zip>>
* creates a tag of form `sha-<sha>`
* upload to GitHub with link:release-create-github[]
Cloning a clean tree is ideal as it generates clean images since <<remove-buildroot-packages,it is not possible to remove Buildroot packages>>
This should in particular enable to easily update <<prebuilt>>.
TODO also run tests and only release if they pass.
===== release-zip
Create a zip containing all files required for <<prebuilt>>