| 1 |
Build instructions: |
| 2 |
|
| 3 |
1. install cmake |
| 4 |
2. mkdir build |
| 5 |
3. cd build |
| 6 |
4. cmake .. |
| 7 |
5. make install |
| 8 |
|
| 9 |
cmake Options: |
| 10 |
-DBUILD_SHARED_LIBS |
| 11 |
By default SHARED libraries are created and applications are linked to it. |
| 12 |
Use -DBUILD_SHARED_LIBS=OFF while invoking cmake to create STATIC libraries |
| 13 |
and link applications to it. |
| 14 |
|
| 15 |
Ex. cmake -DBUILD_SHARED_LIBS=OFF .. |
| 16 |
|
| 17 |
-DCMAKE_INSTALL_PREFIX |
| 18 |
Default is to install to /usr/local, use -DCMAKE_INSTALL_PREFIX= |
| 19 |
when invoking cmake to specify another install location. |
| 20 |
|
| 21 |
-DCMAKE_INSTALL_LIBDIR |
| 22 |
Default is to install to lib or lib64, use -DCMAKE_INSTALL_LIBDIR= |
| 23 |
when invoking cmake to specify another install location. |
| 24 |
|
| 25 |
You may need to update the libbpf git submodule: |
| 26 |
|
| 27 |
git submodule update --init --recursive |
| 28 |
|
| 29 |
Testing: |
| 30 |
|
| 31 |
Tests are available in the tests subdirectory and should be run prior to |
| 32 |
submitting patches. Patches that add functionality should add to tests |
| 33 |
here also. Tests can be run by |
| 34 |
|
| 35 |
- running the scripts directly using a pre-existing vmlinux binary; i.e. |
| 36 |
cd tests ; vmlinux=/path/2/vmlinux ./tests |
| 37 |
(the vmlinux binary must contain DWARF to be converted to BTF) |
| 38 |
|
| 39 |
- running the tests via local scripts in .github/scripts; i.e. |
| 40 |
bash .github/scripts/build-pahole.sh; \ |
| 41 |
bash .github/scripts/build-kernel.sh; \ |
| 42 |
bash .github/scripts/run-selftests.sh |
| 43 |
- via GitHub actions: push a branch to a GitHub repo; actions will be |
| 44 |
triggered for build and test matching the above steps. See the "Actions" |
| 45 |
tab in the github repo for info on job pass/fail and logs. |