Ignore the generated lexer/parser files for the Silverlight-based compiler.
Merge pull request #195 from jack-pappas/master

Ignore generated lexer/parser files for the Silverlight-based compiler.
Excluded BigInteger from Portable
install: avoid using DESTDIR in .Targets files

$DESTDIR is only meant to be a prefix to the prefix specified
by the user, at install time. That is, if the prefix specified
was /usr, and $DESTDIR is assigned the value /tmp when running
the target 'make install', then all the files installed should
be in /tmp/usr, but their contents should never reference this
temporal path /tmp/usr, but /usr, because DESTDIR is only
meant to be used as a hook to where leave the binaries generated
for a certain prefix.

Fixes github issue #204, reported by Henrik Feldt.
Excluded BigInteger from Portable tests
Merge pull request #205 from 7sharp9/fsharp_31

Excluded BigInteger from Portable testing
Excluded Big Integer from Portable.
Merge pull request #207 from 7sharp9/fsharp_31

Excluded Big Integer from Portable.
Merge pull request #206 from knocte/master

install: avoid using DESTDIR in .Targets files
Fix bootstrap on Mono

Bootstrapping on Mono results in various errors and warnings:

1. The reference for the F# library is FSharp.Core, not Fsharp.Core

2. protodir must end with a '/', otherwise FSharp.Core.dll will be
   copied to protoFSharp.Core.dll (which will not be found later on)

3. sigdata and optdata should be copied when copying FSharp.Core.dll

4. fsc-proto must be marked executable, otherwise xbuild will refuse
   to run it

5. FSharp.Core is only needed to run fsc-proto, but placing it in the
   correct directory before any of the build-proto steps silences
   quite a few warnings about the missing "FSharp.Core reference"
Merge pull request #208 from ranma42/fix_bootstrap_31

Bootstrapping F# 3.1 on a clean Mono does not work
Make fsc.exe and fsi.exe +x
merge latest fixes from master
Merge branch 'fsharp_31' of https://github.com/fsharp/fsharp into fsharp_31
Fix name of fsharpc/fsharpi, as reported here: https://github.com/fsharp/fsharp/pull/208#issuecomment-31112488
Fix inconsistent naming of fsiAnyCpu

On case-sensitive filesystems the
CopyDeployFilesToOutputDirectoryPreserveNewest step of the build of
fsiAnyCpu would fail because fsiAnyCpu.exe.config was named
fsiAnyCPU.exe.config:

/usr/lib/mono/4.0/Microsoft.Common.targets: error : Cannot copy
.../fsharp/src/fsharp/fsiAnyCpu/fsiAnyCpu.exe.config to
.../fsharp/lib/release/fsiAnyCpu.exe.config, as the source file
doesn't exist.

Renaming it and the fsproj makes camel-case use more consistent and
fixes the error.
removed unused file, same filename different case
add travis build
Merge pull request #209 from enricosada/fix_fsharp_targets

Microsoft.FSharp.targets or Microsoft.FSharp.Targets
remove targets files which are not needed or have conflicting names