FIP Setup
Linux
Arch
The Flint packages have been published to the AUR. The PKGBUILD is just a small wrapper which downloads the correct binary and puts it into the right path (/usr/bin/). To download and install the fip-c-bin package with the AUR helper of your choice:
paru -Sy fip-c-bin
You may need to restart your shell for the binary to become available after installation.
Fedora
The Flint packages have been published to a COPR repository. To install the C Interop Module you first need to add the COPR repository to dnf and then you can install the package:
sudo dnf copr enable zweiler1/fip-c
sudo dnf install fip-c
You may need to restart your shell for the binary to become available after installation.
Nixpkgs
The C Interop Module, just like the main compiler, is still a work in progress to get published on nixpkgs, use manual installation for now.
Ubuntu
I simply cannot publish anything on Launchpad since I never recieve the verification E-Mail, no matter what I try. I would appreciate some help if you have some experience with launching packages on Launchpad.
Manual Installation
Download the fip-c binary from the Releases page of the fip repository. When executing flintc --version you should see the Flint Interop Protocol version printed in there. You need to grab the Interop Modules which match that version.
Once you have downloaded the fip-c binary simply put it in a directory which is available to the $PATH variable, it is recommended to put it to the flintc into the $HOME/.local/bin/ directory. Then make sure that the binary is executable with chmod +x $HOME/.local/bin/fip-c and you are good to go.
Windows
The C Interop Module for the Flint Interop Protocol is broken currently
The fip-c IM is broken on Windows at the moment. I am glad that I got the compiler to fully work on Windows again, but something about the fip-c IM is completely broken on Windows, and I just do not know what it is. I hope this will get resolved soon. Until then, there is no user-defined automatic FIP-based C interop on Windows.
A workaround is to use the --no-fip flag for the time being. So, you need to manually write out the extern def ... functions, manually compile the C program to a .o file and then use the --flags="..." flag to pass the .o file path to the linker so that it links the file together with your built program.
It just shows how much FIP and the entire system does for you in terms of interop. I hope to get it fixed within the next release.
Winget
winget install Flint.Fip-C
Manual Installation
Download the fip-c.exe executable from the Releases page of the fip repository. When executing flintc --version you should see the Flint Interop Protocol version printed in there. You need to grab the Interop Modules which match that version.
You need to make sure that the fip-c.exe file is contained in a directory which is added to the %PATH% variable of Windows. It's recommended to put it into the %LOCALAPPDATA%\Flint directory, since this directory has been added to the %PATH% variable already if you installed Flint using the installer.