Cross compilation: Difference between revisions

Line 2:

Explain the process of creating, for example, a Linux executable binary on a Windows machine, and vice versa.<br>

Include details of any and all compilation and runtime options for incorporating platform-specific elements.<br>

Use the header <nowiki>===baked in===</nowiki> if the standard distribution contains everything needed, or

<nowiki>===third party===</nowiki> if it depends on another toolchain such as GCC and additional setup/installation

for that.<br>

If your language cannot create executable files or is not cross-platform it should be omitted from this task.

__TOC__

=={{header|FreeBASIC}}==

===third party===

The FreeBASIC compiler supports all compilation targets. You only need to install one fbc per host system, and it can be used to compile both native and non-native programs.

Line 23:

Line 30:

=={{header|Phix}}==

===baked in===

A simple format directive in the source allows for easy cross-compilation to any other supported system, for

instance the Linux binaries of Phix are always compiled on Windows by throwing the following at "p -c -norun p32.exu"

Line 50:

Line 58:

=={{header|Wren}}==

===third party===

Wren is basically a scripting language which lives inside a host application in the form of a virtual machine (VM). The host application communicates with the VM via the embedding API which (like the VM itself) is written in C99.