Difference between revisions of "Cross-compilation from Win32 to GO32v2/hu"
From Lazarus wiki
Jump to navigationJump to searchm (New page: {{Cross-compilation from Win32 to GO32v2}} Hamarosan...<!--In general, FPC support of cross-compilation expects you to have "cross-tools" (assembler and linker), i.e. tools running on the...) |
m |
||
| Line 1: | Line 1: | ||
| − | {{Cross-compilation from Win32 to GO32v2}} | + | {{Translate}}<!--{{Cross-compilation from Win32 to GO32v2}}--> |
Hamarosan...<!--In general, FPC support of cross-compilation expects you to have "cross-tools" (assembler and linker), i.e. tools running on the source platform, but creating binaries for (a different) target platform in your usual "bin" directory (i.e. i386-win32 for your Win32 installation). Filenames of these tools should be prefixed with the target platform specification (e.g. "i386-linux-as.exe" or "i386-go32v2-ld.exe"). | Hamarosan...<!--In general, FPC support of cross-compilation expects you to have "cross-tools" (assembler and linker), i.e. tools running on the source platform, but creating binaries for (a different) target platform in your usual "bin" directory (i.e. i386-win32 for your Win32 installation). Filenames of these tools should be prefixed with the target platform specification (e.g. "i386-linux-as.exe" or "i386-go32v2-ld.exe"). | ||
Revision as of 14:07, 6 June 2009
Hamarosan...
