Skip to content

install.sh: prefix cross-compile outputs with gopacket- #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
psycep merged 1 commit into from
Apr 22, 2026
Merged

install.sh: prefix cross-compile outputs with gopacket- #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion install.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,20 @@ build_target() {
continue
fi
echo -n " ${tool}... "
local out_path="${outdir}/${tool}${exe_suffix}"
# Cross-compile outputs get the same gopacket- prefix as the native
# install, so users copying a .exe to a Windows host don't end up with
# ping.exe / net.exe / reg.exe shadowing built-ins of the same name.
# Native stays as the raw name here; install_native prefixes when it
# copies to INSTALL_DIR.
local out_name
if [ "$t" = "native" ]; then
out_name="$tool"
else
local normalized
normalized=$(echo "$tool" | tr '[:upper:]' '[:lower:]' | tr '_' '-')
out_name="gopacket-${normalized}"
fi
local out_path="${outdir}/${out_name}${exe_suffix}"
local build_cmd=(go build -o "$out_path")
if [ "$t" = "native" ]; then
# Static-link libgcc so binaries run on minimally-versioned hosts.
Expand Down