The main purpose of this repository is to deliver extra packagings of the F# compiler, core library and core tools for use in different settings. The F# community use this repo and others to publish components that augment those available from other vendors, including:
- FSharp.Compiler.Tools NuGet package (this repo)
- FSharp.Core NuGet package (this repo)
- FSharp.Compiler.Service NuGet package (derivative repo)
- “fsharp” Debian Linux packges for F# + Mono (derivative repo)
- “fsharp” as bundled in OSX tooling for F# + Mono by Xamarin
- “fsharp” docker image related repo
- “fsharp” homebrew formula, part of the mono homebrew formula
See notes below for most of these. In theory an unlimited number of other packagings of F# are possible. Please contribute additional notes to this README.md if you are packaging F# for other settings.
Most contributions to the F# compiler/library/tools go first via the
repository at https://github.com/Microsoft/visualfsharp. This ensures that the main
packaging of F# on Windows (the Visual F# Tools) also includes any contributions that are made, and
ensures that the versions do not diverge, and that very extensive QA is done.
If you are using Windows, you should fork the https://github.com/Microsoft/visualfsharp repo and contribute directly there. Your contributions will then be merged into this repo.
If you are using Linux or OSX, you can contribute directly to https://github.com/Microsoft/visualfsharp if you like. CI for that repo runs on Linux. Your contributions will then be merged into this repo. Alternatively, you can prepare your contributions by forking this repository (the code is essentially the same). This will give you access to some additional testing available from this repo.
The master branch is for F# 4.x. To bootstrap the compiler, binaries built from an earlier version of this project are used. This codebase uses the Apache 2.0 license.
| F# | Branch | OSX/Linux | Windows |
|---|---|---|---|
| 4.1+ | master |
 |
|
| 4.0 | fsharp4 |
 |
This repo is currently used to make the FSharp.Core NuGet package. This package includes
- FSharp.Core.dll for .NET Framework/Mono
- FSharp.Core.dll for .NET Core
- FSharp.Core.dll for portable profiles
The FSharp.Core NuGet package includes all of the FSharp.Core redistributables from Visual F#. In addition, they include assemblies for MonoAndroid and MonoTouch built from this repository.
This repo is currently used to make [the FSharp.Compiler.Tools NuGet package]((http://www.nuget.org/packages/FSharp.Compiler.Tools). This package includes the following for both .NET Core and .NET Framework/Mono:
- the F# compiler
fsc.exe - F# Interactive
fsi.exe - build support,
- a copy of FSharp.Core used to run the tools
- related DLLs.
The NuGet packages are exactly the ones produced by AppVeyor CI, e.g. for version 4.1.2. They are pushed to http://nuget.org by someone with appropriate permissions.
The FSharp.Compiler.Tools NuGet package can be used if you wish to use the latest F# compiler on a computer without relying on the installed version of Visual Studio.
Adding it via nuget to a project will override the in-box compiler with the compiler from the nuget package.
Note: you will need to manually modify your project file once (see fsharp#676).
Usage: See http://fsharp.org/use/linux
apt-get install fsharp
See the mono packaging repo, which is a downstream variant of this repo, where this package is actually made.
- There is a tag for each upstream source tag
- There is a tag for each "debianized" package
- Packaging metadata lives in debian/
- install files are files installed to disk
- cligacinstall are GAC-installed libraries
controlis the manifest of packages- rules is the Makefile which handles build/install.
Jo Shields (@directhex) has done much of this work and says:
I tend to only update the published packages when a) the same update has already been pulled in on Mac by Jason, and either b) something breaks horribly in the existing version on a new Mono, or c) someone explicitly asks me to.
Linux package delivery is (now) based on packages built on our public Jenkins instance, and published automatically as a post-build step, based on two inputs - a Git repository in standard Debian git packaging format (which https://github.com/mono/linux-packaging-fsharp already is), and a tarball to consider as the canonical source of the next release (giving the same tarball in subsequent builds is how you indicate packaging-only changes such as alterations to metadata in debian/)
Alexander Köplinger has admin access to Jenkins, SSH access to the Jenkins and repository servers, and has taken care of things for me in my absence in the past (but isn't a Debian packaging expert, so would be trusting that metadata changes are solid)
F# is pacakged as part of Mono on OSX. Jason Imison says:
We use a system called BockBuild that pushes versions of F# (sometimes with patches) out with Mono for OSX (F# is bundled with mono here, not a separate package).
You can see an example build script here (if you have access, ping me if not) https://github.com/xamarin/bockbuild/blob/2017-02/packages/fsharp.py. Unfortunately, you need to know the branch name here – 2017-02 is what is going to be released with VS for Mac aka Mono 4.9.x
We build fsharp/fsharp internally so that we’re not dependent on you pushing out fixes / bumping packages. Miguel de Icaza likes to ‘own’ the code that we ship precisely to stop these kind of emergency issues.
@cartermp says:
For future reference, dependencies and code for the F# editing and F# Interactive support in Visual Studio for Mac/Xamaring Studio) is here
A feed of nuget packages from builds is available from AppVeyor using the NuGet feed: https://ci.appveyor.com/nuget/fsgit-fsharp
If using Paket, add the source at the top of paket.dependencies.
source https://www.nuget.org/api/v2
source https://ci.appveyor.com/nuget/fsgit-fsharp
Add the dependency on FSharp.Core and run paket update. See the AppVeyor build history for a list of available versions. Here are some options for specifying the dependency:
nuget FSharp.Core
nuget FSharp.Core prerelease
nuget FSharp.Core 3.1.2.3
nuget FSharp.Core 3.1.2.3-b208
If using NuGet Package Manager, add the source to the list of available package sources.
Building F# on Unix-type platforms requires
Mono 4.4 or higher. If you
get a complaint in subsequent steps about xbuild being missing, it means
you don't have Mono installed.
Building on OS X requires several development tools that are not installed by default. Most can be installed via Homebrew:
brew install autoconf automake pkg-config
Building on OS X also requires Xcode. If you don't want to install the full GUI development environment, the command line tools are sufficient. At a shell prompt, say:
xcode-select --install
The usual:
./autogen.sh --prefix=/usr
make
sudo make install
By default that makes optimized binaries. To make debug, use make CONFIG=debug
Use a prefix to your version of Mono:
./autogen.sh --prefix=/Library/Frameworks/Mono.framework/Versions/Current/
make
sudo make install
By default that makes optimized binaries. To make debug, use make CONFIG=debug
Build using:
build.bat
This build the proto compiler, then the library, then the final compiler.
The FSharp.Core.dll produced is only delay-signed (Mono does not require strong names). If a strong-name signed FSharp.Core.dll is needed then use the one in
lib\bootstrap\signed\.NETFramework\v4.0\4.3.0.0\FSharp.Core.dll
lib\bootstrap\signed\.NETFramework\v4.0\4.3.1.0\FSharp.Core.dll
vagrant up
vagrant ssh
cd /vagrant
sudo apt-get install dos2unix autoconf
./autogen.sh --prefix=/usr
make
sudo make install
To integrate latest changes from https://github.com/Microsoft/visualfsharp, use
git remote add visualfsharp https://github.com/Microsoft/visualfsharp
git pull visualfsharp master
There are certain guidelines that need to be followed when integrating changes from upstream:
- this repository does not undergo the QA test process that upstream does, so the
tests/fsharpqafolder and all files within should be removed when merging - this repository does not contain any of the Visual Studio tooling or integrations, so the
vsintegrationdirectory and all files within should be removed when merging - anything referencing
FSharp.LaunguageService.Compileris a Microsoft-internal version of the open FSharp.Compiler.Service repository, and should be removed when merging - Windows-specific scrips like
update.cmdandruntests.cmdaren't used in this repository, and so should be removed when merging
A continuous integration build is set up with Travis and AppVeyor. See above.
Historically it is difficult to edit the compiler with Xamarin Studio or MonoDevelop because of bugs in loading the hand-edited project files and targets used in the F# compiler build. These are generally in the process of being fixed, your mileage will vary.
Only a subset of the tests are currently enabled.
After building and installing, run
cd tests/fsharp/core
./run-all.sh
See the TESTGUIDE.md for instructions for how to test on Windows. Use that repository to develop and test on Windows.
F# compiler sources as initially dropped are available from fsharppowerpack.codeplex.com.
On 4 April 2014, Microsoft Open Tech published the F# compiler sources at http://visualfsharp.codeplex.com and began accepting contributions to the F# compiler/library and tools.
In 2016 the Microsoft http://visualfsharp.codeplex.com repo moved to GitHub at http://github.com/Microsoft/visualfsharp.
This repository uses bootstrapping libraries, tools and F# compiler. The lib/bootstrap/X.0 directories contain mono-built libraries, compiler and tools that can be used to bootstrap a build. You can also supply your own via the --with-bootstrap option.
The maintainers of this repository appointed by the F# Core Engineering Group are:
- Enrico Sada, Don Syme
- with help and guidance from Tomas Petricek, Robin Neatherway, Cameron Taggart, Dave Thomas, Jo Shields, Kevin Ransom and Henrik Feldt and many others