-
Notifications
You must be signed in to change notification settings - Fork 106
Use xbuild by default in F# for MonoDevelop #34
Comments
I thought that the Xbuild support was handled by the F# addin? |
What issue are you having with xbuild support? It's the sole build engine for our Android product for more than a year now. |
I'm going to be compiling more projects using xbuild later today. For example I'll try to bootstrap the F# compiler using xbuild. -- ben |
Yes, you're right, it's using it as the default if you enable xbuild. All looks good now, I'm compiling F# projects happily using xbuild after latest F# fixes - tag 3.0.6 in https://github.com/fsharp/fsharp |
My point was that you can force f# projects to always build with xbuild regardless of the IDE setting. This is probably what you want to do. |
Sounds right. Any idea how we do that? Now the fsharpbinding implements IDotNetLanguageBinding and overrides Compile with some logic which cracks the project file etc. on its own Do we replace this by an invocation of xbuild? If so, do you know where there some sample code for that? -- ben p.s. another one problem we have is that FSharp.Core is showing up as undefined in MonoDevelop's solution pad (though xbuild finds it on a build). If you know anything about that would be grateful for pointers #30 |
@mhutch, What's the correct way to opt all F# projects in to using XBuild by default? |
useXBuild="true" on the DotNetProjectSubtype where the targets are registered |
They use a DotNetProject, not a DotNetProjectSubtype |
We can change if you think it is the right thing to do to move things |
Not sure of the status of xbuild support, supposedly it is much improved in Mono 3.0.
We need to see if it is ok and if we should use it instead of all the current hacking we do.
The text was updated successfully, but these errors were encountered: