build runs, lots of uncommented and lots of untested though

Refactor everything. Create nice submodules/ and packages/ folders.
This commit is contained in:
Ciro Santilli
2018-09-07 10:08:59 +01:00
parent 5796f1ee1d
commit 66fe5f6647
123 changed files with 262 additions and 233 deletions

13
configure vendored
View File

@@ -11,7 +11,7 @@ while getopts gpqt OPT; do
gem5=true
;;
p)
submodules="$submodules parsec-benchmark/parsec-benchmark"
submodules="${submodules} parsec-benchmark"
;;
q)
qemu=false
@@ -100,10 +100,10 @@ fi
## Submodules
if "$qemu"; then
submodules="$submodules qemu"
submodules="${submodules} qemu"
fi
if "$gem5"; then
submodules="$submodules gem5/gem5"
submodules="${submodules} gem5"
fi
(
set -e
@@ -113,10 +113,11 @@ fi
# In particular:
# - `shallow = true` on the submodule has no effect for the non default educational branches of our submodules
# - QEMU's submodules point to commits that are neither under branches nor tags, and so `--shallow-submodules` fails
git submodule update --depth 1 $gitjobs --init -- $submodules
for submodule in submodules/*/; do
git submodule update --depth 1 $gitjobs --init -- "submodules/${submodule}"
done
if "$qemu"; then
cd qemu
git submodule update --init --recursive
git -C submodules/qemu submodule update --init --recursive
fi
) &
# https://unix.stackexchange.com/questions/65532/why-does-set-e-not-work-inside-subshells-with-parenthesis-followed-by-an-or