-
Notifications
You must be signed in to change notification settings - Fork 106
Type providers not compiling on MonoDevelop #67
Comments
Look carefully in the references list: it's not finding FSharp.Core, which may be related to the issue. |
Dont worry about that, its always shown like that due to an issue with the pkgconfig, thats issue #30 |
To be honest I dont think this is an issue with the binding anymore, Ill leave it here until I get to the bottom of the issue though... |
A while back someone helped us make a couple of type providers "cross platform" on Mono/MonoDevelop. Here are the notes: First, a type provider on Mono can expose some small differences in Mono and .NET, especially in the System.Type implementation. The ProvidedTypes API can normally be adjusted to account for these. To help isolate the problem, try the following:
In any case, switching to command-line compilations will help localize the problem. |
Thanks @dsyme One of the main problems is debugging the issues. I found the main issue was the errors reported didn't reflect the problem. It looked like the problem was with with the compiler not being passed the types, but the real issue was with path differences between osx and windows. Whats Ill do is transfer this issue to the fsharpx repo. One thing I have noticed is that intellisense seems to be extremely limited around the nested functions in the type providers, Ill see if I can localise this too and raise an issue in the binding. |
@dsyme Maybe we should extend the advice above and include it in the new documentation we are planning (we being fsharp.org) |
Good point. I've copied them into some working notes for a x-plat development guide and will send you a copy of the collected notes I have. |
El capitan fixes
Type providers appear to work initially but on compilation non defined member errors are shown.
This effects MonoDevelop 3.05 stable and 3.06 beta. This is with the 3.2.10 binding from the gallery.
Could this be related to compilation order as intellisense works ok. Its as if the compilation phase is not getting the generated output from the type provider.
Its possible that this may be a fault in the fsharpx type providers as the Regex, Maths, and freebase providers seem to compile ok. This could simply be a cross platform issue for fsharpx. If so I can move this issue over there...
The text was updated successfully, but these errors were encountered: