Back to Questions
1.3k
views5
comments
Building FParsec on mono? (or how do I reference a dll with -r?)
f#

How can I do this?

I can use xbuild to build FParsecCS, but if I try xbuild on FParsec.fsproj I get the "...Microsoft.FSharp.Targets" does not exist error described (but not resolved) here.

I naively thought I might be able to build FParsec by running `fsc -r FParsecCS.dll Internals.fs Error.fsi Error.fs Primitives.fsi Primitives.fs CharParsers.fsi CharParsers.fs`, but then I get

/FParsec/Internals.fs(33,34): error FS0039: The field, constructor or member 'ContainsNewlineChar' is not defined

followed by a whole bunch of other errors that stem from the same cause

That particular error comes out of

let containsNewlineChar = Helper.ContainsNewlineChar

but Helper.ContainsNewlineChar is defined in FParsecCS. Shouldn't the -r FParsecCS.dll be sufficient to get fsc to "see" that? If not, what do I need to do to reference FParsecCS correctly?

It seems odd that I'm getting this error, since if I don't reference FParsecCS.dll at all, I get many more errors, like " The namespace or module 'Helper' is not defined", so the -r command is obviously doing something.

I can get projects that use FParsec to work on mono by building FParsec in Visual Studio (as long as I don't target .NET 4.0) and then referencing the dlls I get from that in projects on mono, but I'd like to know how to do the same thing without having to run over to my Windows box.

.

Maybe the manual compile doesn't work because somehow the "InternalsVisibleTo" assembly attribute on the FParsecCS assembly isn't honoured. Did you include Properties/AssemblyInfo.cs when you compiled FParsecCS?

By on 9/19/2010 8:06 AM ()

I think so, since it's in the csproj file, so xbuild should have caught it. Just to make sure that wasn't the problem, I tried using the FParsec dll that I build in VS, and I got the same error.

I noticed that I wasn't include AssemblyInfo.fs when compiling FParsec, but adding that to the list of files didn't change the error, either.

By on 9/19/2010 12:43 PM ()

To make sure it's really not a problem with the InternalsVisibleTo attribute, could you search & replace "internal with "public" in the FParsecCS sources and see if FParsec still fails to compile? Thanks.

By on 9/19/2010 2:54 PM ()

Hmm. It compiled without any errors after I did that. I wonder what I'm doing wrong when I build normally.

By on 9/21/2010 11:16 AM ()

Maybe it's a compiler issue. You could try to make a simple test case with two trivial assemblies and if you don't get it to work, report it to fsbugs@microsoft.com.

By on 9/22/2010 8:48 AM ()

    Topic tags

    IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
    Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy     		Built with WebSharper