3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-25 19:21:35 +01:00
Code Issues Releases Wiki Activity

prebuilt: fix some things

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-01-22 00:00:00 +00:00
parent 515be9a444
commit 0be47d96b5
1 changed files with 19 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
README.adoc
View File

@@ -554,9 +554,13 @@ git submodule update --depth 1 --init --recursive "$(./getvar linux_source_dir)"
./run
....
`modules_prepare` does the minimal build procedure required on the kernel for us to be able to compile the kernel modules, and is way faster than doing a full kernel build. A full kernel build would also work however.
TODO: for now the only way to test those modules out without <<qemu-buildroot-setup-getting-started,building Buildroot>> is with 9p, since we currently rely on Buildroot to manipulate the root filesystem.
This command automatically falls back to the Ubuntu packaged GCC since you don't have the Buildroot toolchain.
Command explanation:
* `modules_prepare` does the minimal build procedure required on the kernel for us to be able to compile the kernel modules, and is way faster than doing a full kernel build. A full kernel build would also work however.
* the `./build-modules` command automatically falls back to the Ubuntu packaged GCC since you don't have the Buildroot toolchain
* `--no-modules-install` is required otherwise the `make modules_install` target we run by default fails, since the kernel wasn't built
To modify the Linux kernel, build and use it as usual:
@@ -12214,7 +12218,7 @@ git push --follow-tags
./release-upload
....
Do an out-of-box testing for the release candidate:
Now let's do an out-of-box testing for the release candidate:
....
cd ..
@@ -12222,7 +12226,18 @@ git clone https://github.com/cirosantilli/linux-kernel-module-cheat linux-kernel
cd linux-kernel-module-cheat-release
....
Test <<prebuilt>>, and then through all of the <<getting-started>> section in order.
Test <<prebuilt>>.
Clean up, and re-start from scratch:
....
cd ..
rm -rf linux-kernel-module-cheat-release
git clone https://github.com/cirosantilli/linux-kernel-module-cheat linux-kernel-module-cheat-release
cd linux-kernel-module-cheat-release
....
Go through all the other <<getting-started>> sections in order.
Once everything looks fine, publish the release with: