* {{AUR|fpc-multilib}} is available from the [[Arch User Repository]] which provides an x86_64 host compiler targetting both i686 and x86_64 CPU Linuxes. This will also provide the {{AUR|ppcross386}} FPC compiler driver package.

* {{AUR|fpc-multilib}} is available from the [[Arch User Repository]] which provides an x86_64 host compiler targetting both i686 and x86_64 CPU Linuxes. This will also provide the {{AUR|ppcross386}} FPC compiler driver package.

==== Cross compilers ====

==== Cross compilers ====

+

* {{AUR|fpc-arm-android-rtl}} for ARM-based Android (beta)

* {{AUR|fpc-arm-linux-rtl}} for ARM-based Linux

* {{AUR|fpc-arm-linux-rtl}} for ARM-based Linux

* {{AUR|fpc-arm-wince-rtl}} for MS Windows CE

* {{AUR|fpc-arm-wince-rtl}} for MS Windows CE

+

* {{AUR|fpc-i386-android-rtl}} for i386-based Android (beta)

* {{AUR|fpc-i386-freebsd-rtl}} for 32-bit Intel FreeBSD

* {{AUR|fpc-i386-freebsd-rtl}} for 32-bit Intel FreeBSD

* {{AUR|fpc-i386-win32-rtl}} for 32-bit MS Windows

* {{AUR|fpc-i386-win32-rtl}} for 32-bit MS Windows

Revision as of 09:03, 26 October 2013

This page explains on how to write PKGBUILDs for software built with the Free Pascal Compiler (FPC). There currently exists two options for building software of Linux, as well as a handful of options for building software on other targets using FPC cross compilers:

Contents

Arch Linux

fpc is available in the official Arch community repository and provides a compiler targetting only your host CPU (i686 or x86_64).

fpc-multilibAUR is available from the Arch User Repository which provides an x86_64 host compiler targetting both i686 and x86_64 CPU Linuxes. This will also provide the ppcross386AUR FPC compiler driver package.

Free Pascal

Package naming

The project name alone is usually sufficient. However, in the case of cross-compiling, the package should be prefixed with fpc32- when targetting i686 Linux from multilib and named in the format of fpc-cpu-system-pkgname when targetting non-Arch Linux systems.