LailaTheElf/actions-rust-cross
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add comment to remind myself why we need cross for Linux i586/i686 targets

Browse Source
This commit is contained in:
Dave Rolsky 2025-02-16 11:11:06 -06:00
parent dc1022bc69
commit 9a022034a6
No known key found for this signature in database
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
set-cross-compile.py
View File

@ -61,6 +61,10 @@ def check_needs_cross(target: str) -> bool:
): ):
return False return False
# It's tempting to not use cross when the host is Linux x86-64 and we're compiling for Linux
# i586 or i686. This sort of works, but if there's any C being compiled, things get weird,
# because then we need 32-bit C headers, 32-bit C libs to link to, etc.
# Check if both host and target are ARM Linux. I'm assuming here that for things like # Check if both host and target are ARM Linux. I'm assuming here that for things like
# "arm-linux-androideabi" or "armv7-unknown-linux-ohos" we'd still need cross. # "arm-linux-androideabi" or "armv7-unknown-linux-ohos" we'd still need cross.
if ( if (