raspberry:cross-platform-compile:cross-compile-overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| raspberry:cross-platform-compile:cross-compile-overview [2026/09/02 20:42] – [The problem with different host and target ARM libraries] oscar | raspberry:cross-platform-compile:cross-compile-overview [2026/09/04 12:41] (current) – [Cross Platform Development for Raspberry] oscar | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| - **Different Linux/ | - **Different Linux/ | ||
| - | - [[raspberry: | + | - [[raspberry: |
| - | - [[raspberry: | + | |
| - | [[raspberry: | + | - [[raspberry: |
| - | ===== Compatibility rule ===== | + | |
| - | Build against the oldest operating-system release and CPU that the resulting | + | |
| - | binary must support. | + | |
| - | Do not link a Bookworm target against Trixie ARM libraries. Doing so can create | + | - [[raspberry: |
| - | dependencies on newer glibc or library symbols that are unavailable on the | + | |
| - | Bookworm target. | + | |
| - | For example: | ||
| + | ===== Compatibility rule ===== | ||
| + | Build against the oldest operating-system release and CPU that the resulting | ||
| + | binary must support. Do not link a Bookworm target against Trixie ARM libraries. Doing so can create | ||
| + | dependencies on newer glibc or library symbols that are unavailable on the | ||
| + | Bookworm target. For example: | ||
| < | < | ||
| Incorrect: | Incorrect: | ||
raspberry/cross-platform-compile/cross-compile-overview.1788381737.txt.gz · Last modified: by oscar
