Support cross-architecture deployment by auto-detecting target binary architecture #338

Activity

1. novumdxw commented on Aug 15, 2026

   

   novumdxw

   on Aug 15, 2026

   Last edited by novumdxw

   Author

   More actions

   I read build.sh and found the following code.

   patchelf_path="$(which patchelf)"
   strip_path="$(which strip)"
   linuxdeploy_args=(
       --appdir AppDir
       -e bin/linuxdeploy
       -i "$repo_root/resources/linuxdeploy.png"
       -d "$repo_root/resources/linuxdeploy.desktop"
       -e "$patchelf_path"
       -e "$strip_path"
   )
   
   # deploy patchelf which is a dependency of linuxdeploy
   bin/linuxdeploy "${linuxdeploy_args[@]}"
   

   I guess the linuxdeploy tool uses the host system's patchelf and strip to bundle the dependencies.
2. novumdxw commented on Aug 15, 2026

   

   novumdxw

   on Aug 15, 2026

   Author

   More actions

   I checked and found that the linux distributions (Ubuntu, Fedora, Arch) use triple-foo as the CLI tool name.

   As shown in the file listings of the following package URLs, the strip tool is named aarch64-linux-gnu-strip across all three distributions.
   Ubuntu-binutils-aarch64-linux-gnu
   Fedora-binutils-aarch64-linux-gnu
   Arch-aarch64-linux-gnu-binutils

   Shouldn't we let the user decide which patchelfand strip to use?