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 11:11:35 +01:00
Code Issues Releases Wiki Activity

gem5: replace --gem5-src with --gem5-worktree-path

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2018-09-28 00:00:00 +00:00
parent f403f86934
commit ca55bc2d61
3 changed files with 30 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.adoc
View File

@@ -10667,32 +10667,28 @@ Even removing remotes is not safe enough, since `git submodule update` and other
Instead, we provide the following safer process.
First do a separate private clone of you private repository:
First do a separate private clone of you private repository outside of this repository:
....
git clone https://my.private.repo.com/my-fork/gem5.git gem5-internal
gem5_internal="$(pwd)/gem5-internal"
....
Next, when you want to build with this repository, use the `--gem5-src` argument to point this repository to the private source code:
Next, when you want to build with this repository, use the `--gem5-worktree-path` argument to point this repository to the private source code:
....
cd linux-kernel-module-cheat
./build-gem5 \
--gem5-build-id private/master \
--gem5-src "$gem5_internal" \
--gem5-worktree private/master \
--gem5-worktree-path "$gem5_internal" \
;
./run-gem5
--gem5-build-id private/master \
--gem5-src "$gem5_internal" \
--gem5-worktree private/master \
--gem5-worktree-path "$gem5_internal" \
;
....
`private` is not mandatory, but it is a sane default that will remind you at all times that you are dealing with private code instead of public.
This setup only creates gitignored worktrees of the private repository inside this repository, which is pretty safe, while still allowing fully use our infrastructure as usual.
With this setup, only the private gem5 build outputs are stored in this repository, and they are safely gitignored.
===== gem5 debug build