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

build-userland-in-tree is now a Python command

Browse Source 
./build calls it, we did this to allow --download-dependencies to work
perfectly.
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-05-05 00:00:00 +00:00
parent aea97698c3
commit 9c8f95d630
5 changed files with 75 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.adoc
View File

@@ -996,7 +996,7 @@ Build the current directory:
./build
....
Note however that this would try to build the link:userland/libs/[] folder, which depends on certain libraries being installed on the host, e.g. <<blas>>.
Note however that if you run this from link:userland/[] toplevel, it would try to build the link:userland/libs/[] folder, which depends on certain libraries being installed on the host, e.g. <<blas>>.
You can install those libraries and do the build in one go with:
@@ -1011,7 +1011,17 @@ If you modify a dependency that is not currently considered such as a header fil
./build --force-rebuild
....
Do a more clean out of tree build and run the program instead:
The `build` scripts inside link:userland/[] are just symlinks to link:build-userland-in-tree[] which you can also use from toplevel as:
....
./build-userland-in-tree
./build-userland-in-tree c
./build-userland-in-tree c/hello.c
....
which is in turn just a thin wrapper around link:build-userland[], so you can use any option supported by that script freely.
Do a more clean out-of-tree build and run the program instead:
....
./build-userland --gcc-which host --userland-build-id host