Permalink
Commits on Nov 10, 2012
  1. copy and install xml files

    funnelweb committed Nov 10, 2012
    This gives documentation for FSharp.Core.dll in MonoDevelop
  2. fix build break

    funnelweb committed Nov 10, 2012
Commits on Nov 9, 2012
  1. reduce noise during build

    funnelweb committed Nov 9, 2012
Commits on Nov 8, 2012
Commits on Nov 7, 2012
Commits on Nov 6, 2012
  1. configure.ac: Mono 2.11.5 == 3.0

    knocte committed Nov 6, 2012
    Mono version 2.11.5 was never released and was actually renamed to 3.0
  2. Reenable pkgconfig check for mono, but reducing bloat

    knocte committed Nov 6, 2012
    In case you need a clarification wrt bloat:
    http://tirania.org/blog/archive/2012/Oct-20.html
Commits on Nov 5, 2012
  1. Make mono/xbuild F# resource naming a bit more consistent with Visual F#

    funnelweb committed Nov 5, 2012
    See #50
    
    The comments in FSharpBuild/Fsc.fs explain a bit more. It is realy hard
    to work out how to make this perfectly consistent. Essentially, be
    careful using resources in folders if you want your projects to be
    portable across VisualStudio/MSBuild and mono/MonoDevelop/XBuild
    
    We hit this bug in fsharp/fsharpbinding, but we've moved that to no
    longer put resources in folders for now.
Commits on Nov 1, 2012
  1. Update README.md

    funnelweb committed Nov 1, 2012
Commits on Oct 31, 2012
  1. fix banner string

    funnelweb committed Oct 31, 2012
  2. typo in FSharp.Compiler.fsroj

    funnelweb committed Oct 31, 2012
  3. update bootstrap to use signed FSharp.Core

    funnelweb committed Oct 31, 2012
    The FSharp.Core in lib/bootstrap/4.0 needs to be properly strong name
    signed if we'r going to run on Windows without VS installed and without
    FSharp.Core in the GAC
  4. update to previous checkin

    funnelweb committed Oct 31, 2012
  5. typo

    funnelweb committed Oct 31, 2012
  6. Use strong names for bootstrap compiler to help with compile on windows

    funnelweb committed Oct 31, 2012
    switch to strong names for compiler binaries and update the bootstrap
    compiler with those names. The strong names are based on
    src\fsharp\test.snk
    
    this means the strong name for FSharp.Compiler.dll changes, but no one
    should be depending on that and the new names are useful as the won't
    collide with the visual studio versions of these DLLs on windows. The
    monodevelop binding is neutral to the strong names used.
    
    we still compile FSharp.Core as
    delay-signed-with-the-microsoft-key-and-then-mono-key-signed which Mono
    recognizes as strong named but i think windows does not. We have to use
    this identity for FSHarp.Core to keep binary compatibility with
    Windows-compiled thing like type provider DLLs.
    
    We may have to use the Microsoft FSHarp.Core.dll on Windows, i think it
    gets picked up automatically from the GAC but need to check tomorrow.
    
    also fixes bugs in ilsupp.fs in strong nae signing.
    
    tested by bootstrapping, and manually examining the names on the dlls.
Commits on Oct 30, 2012
  1. Revert deliberate build break

    funnelweb committed Oct 30, 2012
  2. xbuild FSharp.Core for Mono 2.1 profile

    funnelweb committed Oct 30, 2012
    We're gradually moving the build to xbuild, this enables the build of
    FSharp.Core for Mono profile 2.1
  3. Cleanup original readme

    funnelweb committed Oct 30, 2012
    Removing .NET 2.0 profile and adding fsharp-build.fsproj
Commits on Oct 29, 2012
Commits on Oct 28, 2012
  1. Always use mono-sgen for /resident background process

    funnelweb committed Oct 28, 2012
    This ensures mono-sgen is used even if fsc.exe is invoked by xbuild.
    
    Aso add tracing diagnostics to /resident startup
  2. additions to .gitignore

    funnelweb committed Oct 28, 2012
  3. Fix banner text

    funnelweb committed Oct 28, 2012