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

build-linux: --no-modules-install

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

7
README.adoc
View File

@@ -539,8 +539,7 @@ You have to checkout to the latest tag to ensure that the scripts match the rele
Be saner and use our custom built QEMU instead:
....
git submodule update --init --recursive "$(./getvar qemu_source_dir)"
./build-qemu
./build --download-dependencies qemu
./run
....
@@ -549,7 +548,8 @@ This also allows you to <<your-first-qemu-hack,modify QEMU>> if you're into that
To build the kernel modules as in <<your-first-kernel-module-hack>> do:
....
./build-linux -- modules_prepare
git submodule update --depth 1 --init --recursive "$(./getvar linux_source_dir)"
./build-linux --no-modules-install -- modules_prepare
./build-modules
./run
....
@@ -561,6 +561,7 @@ This command automatically falls back to the Ubuntu packaged GCC since you don't
To modify the Linux kernel, build and use it as usual:
....
git submodule update --depth 1 --init --recursive "$(./getvar linux_source_dir)"
./build-linux
./run
....

2
build
View File

@@ -246,7 +246,7 @@ so looping over all of them would waste time.
**gem5_deps
),
'linux': _Component(
self._build_file('build-linux', gem5_build_type='fast'),
self._build_file('build-linux'),
dependencies={'buildroot'},
submodules_shallow={'linux'},
apt_get_pkgs={

37
build-linux
View File

@@ -26,6 +26,12 @@ configs. Takes precedence over any config files.
help='''\
Also use the given kernel configuration fragment file.
Pass multiple times to use multiple fragment files.
'''
)
self.add_argument(
'--config-only', default=False,
help='''\
Configure the kernel, but don't build it.
'''
)
self.add_argument(
@@ -44,9 +50,9 @@ Ignore --custom-config-file.
'''
)
self.add_argument(
'--config-only', default=False,
'--modules-install', default=True,
help='''\
Configure the kernel, but don't build it.
Run `make modules_install` after `make`.
'''
)
self.add_argument(
@@ -138,19 +144,20 @@ Configure the kernel, but don't build it.
},
**common_args
)
self.sh.run_cmd(
(
common_make_args +
[
'INSTALL_MOD_PATH={}'.format(self.env['out_rootfs_overlay_dir']), LF,
'modules_install', LF,
]
),
**common_args
)
# TODO: remove build and source https://stackoverflow.com/questions/13578618/what-does-build-and-source-link-do-in-lib-modules-kernel-version
# TODO Basically all kernel modules also basically leak full host paths. Just terrible. Buildroot deals with that stuff nicely for us.
# self.rmrf()
if self.env['modules_install']:
self.sh.run_cmd(
(
common_make_args +
[
'INSTALL_MOD_PATH={}'.format(self.env['out_rootfs_overlay_dir']), LF,
'modules_install', LF,
]
),
**common_args
)
# TODO: remove build and source https://stackoverflow.com/questions/13578618/what-does-build-and-source-link-do-in-lib-modules-kernel-version
# TODO Basically all kernel modules also basically leak full host paths. Just terrible. Buildroot deals with that stuff nicely for us.
# self.rmrf()
def get_build_dir(self):
return self.env['linux_build_dir']