scx-upstream/meson-scripts/fetch_bpftool

#!/bin/bash

URL=https://github.com/libbpf/bpftool.git

cd $1
rm -rf bpftool
git clone --depth=1 ${URL}
cd bpftool
git fetch --depth=1 origin $2 || {
    echo "commit $2 does not exists in ${URL}"
    exit 1
}
git checkout $2
git submodule update --init --recursive
Fetch and build bpftool by default This pairs with the new default behavior to fetch and build libbpf and is mostly being used so we can use the latest bpftool and libbpf. 2024-03-08 19:32:47 +00:00			`#!/bin/bash`

meson: check if commit exists in remote git repos When fetching external git repositories (libbpf and bpftool) we don't check if the target commit exists. This can leads to issues such as #400, because we may silently use HEAD, instead of the specified commit. Prevent this by returning an error when the target SHA1 cannot be found. Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 14:13:38 +01:00			`URL=https://github.com/libbpf/bpftool.git`

Fetch and build bpftool by default This pairs with the new default behavior to fetch and build libbpf and is mostly being used so we can use the latest bpftool and libbpf. 2024-03-08 19:32:47 +00:00			`cd $1`
			`rm -rf bpftool`
meson: check if commit exists in remote git repos When fetching external git repositories (libbpf and bpftool) we don't check if the target commit exists. This can leads to issues such as #400, because we may silently use HEAD, instead of the specified commit. Prevent this by returning an error when the target SHA1 cannot be found. Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 14:13:38 +01:00			`git clone --depth=1 ${URL}`
Fetch and build bpftool by default This pairs with the new default behavior to fetch and build libbpf and is mostly being used so we can use the latest bpftool and libbpf. 2024-03-08 19:32:47 +00:00			`cd bpftool`
meson: check if commit exists in remote git repos When fetching external git repositories (libbpf and bpftool) we don't check if the target commit exists. This can leads to issues such as #400, because we may silently use HEAD, instead of the specified commit. Prevent this by returning an error when the target SHA1 cannot be found. Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 14:13:38 +01:00			`git fetch --depth=1 origin $2 \|\| {`
			`echo "commit $2 does not exists in ${URL}"`
			`exit 1`
			`}`
Fetch and build bpftool by default This pairs with the new default behavior to fetch and build libbpf and is mostly being used so we can use the latest bpftool and libbpf. 2024-03-08 19:32:47 +00:00			`git checkout $2`
meson: check if commit exists in remote git repos When fetching external git repositories (libbpf and bpftool) we don't check if the target commit exists. This can leads to issues such as #400, because we may silently use HEAD, instead of the specified commit. Prevent this by returning an error when the target SHA1 cannot be found. Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 14:13:38 +01:00			`git submodule update --init --recursive`