-
Notifications
You must be signed in to change notification settings - Fork 783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
So ... you want to try out the coreclr version of the compiler on windows #649
Comments
Nah, not windows, osx! |
Tried... got the following error when calling
|
My attempt to build the coreclr branch also failed. I got roughly the same thing trying to build master in the VS2015 console. I'm also running a Windows Server 2012 VM, not Windows 10. Here's the last bit of the output left in my window buffer:
|
Will this make F# with .net native available or that is irrelevant to CoreCLR support ? |
Damn I am getting this build error from the appveyor server, it doesn't repo on any of my machines. |
Hi @KevinRansom - people are asking for FSharp.Compiler.Service to be brought up on CoreCLR, see fsharp/fsharp-compiler-docs#465 (comment). Do you think the core compiler changes CoreCLR branch are now stable enough that it is worth integrating them across to a matching coreclr branch in the FSHarp.Compiler.Service project, and then publishing a prelim nuget package for the compiler service as a CoreCLR-ready component? I think the branch probably is stable enough? |
instead of push Less branch to sync ( master+coreclr on visualfsharp, master+coreclr on openfsharp (xplat right?), master+coreclr on fcs ), really, let's use a build parameters, and is done. If you have fear of breaking, we can use a stabilization branch before update2 ( @KevinRansom or that is the |
Is there a version of FCS which supports it already? If so, is it on a feed somewhere? |
The fcs does not yet support coreclr. |
@KevinRansom if you still have problems with AppVeyor, you can rdp to a worker machine to troubleshot the problem: https://www.appveyor.com/docs/how-to/rdp-to-build-worker |
@KevinRansom Hi Kevin I'd be really interested in getting involved in contributing to the F# project, particularly WRT the CoreCLR. I've noticed there's a very good page here: https://github.com/Microsoft/visualfsharp/wiki/F%23-for-CoreCLR---Status What would be the best way for someone who is new to this community (but an experienced windows/unix developer) to get started contributing in a meaningful way? Thanks, and sorry for hijacking this discussion a bit, if there's a more appropriate place to talk (slack or whatever) please let me know! |
Hey, Thanks for the mail … I just completed support for portable pdbs, and I am currently in the process of checking in the coreclr changes into master both of which are kind of cool. Where we are currently very weak is cross-platform build, whilst the F# compiler runs on linux and mac, and has done so for a long time. We can’t yet build the product there, which still makes me sad. The other area we are hugely weak is cross platform testing, we have some tests that run using nunit on coreclr which is very excellent, it would be nice if we could expand that. @enricosada has been driving forward our dotnet cli integration. The bit that scares me most though is testing, I would really love if we could get a grip on our testing and make sure that as much as feasible can run on the coreclr. We are open to pretty much whatever interests you, open an issue, have a discussion about what you wish to do, mainly to make sure it doesn’t overlap someone else’s interests. And then get to work. Kevin From: Dave Kerr [mailto:notifications@github.com] @KevinRansomhttps://github.com/KevinRansom Hi Kevin I'd be really interested in getting involved in contributing to the F# project, particularly WRT the CoreCLR. I've noticed there's a very good page here: https://github.com/Microsoft/visualfsharp/wiki/F%23-for-CoreCLR---Status What would be the best way for someone who is new to this community (but an experienced windows/unix developer) to get started contributing in a meaningful way? Thanks, and sorry for hijacking this discussion a bit, if there's a more appropriate place to talk (slack or whatever) please let me know! — |
Thanks @KevinRansom appreciate the info! What about chat/communication, is there an IRC or something for the people who are currently working on the project, or is most communication handled on issues themselves? |
The latest getting started docs are here: https://docs.microsoft.com/en-us/dotnet/articles/fsharp/getting-started-netcore I think we can close this discussion? |
Strange, cant find back this issue? On Mon, Jul 11, 2016 at 8:23 PM, Don Syme notifications@github.com wrote:
|
@dsyme the link you provided is currently down. May you please provide the update version or the new replacement. Thank you. Good day. |
[ Edit: latest getting started docs now at https://docs.microsoft.com/en-us/dotnet/articles/fsharp/getting-started-netcore ]
This is probably the easiest way to go about this:
a. The desktop compiler is kind of helpful and will go searching around for mscorlib, fsharp.core.dll etc. This functionality is not yet implemented ... on the desktop it was implemented using msbuild and some custom logic. In coreclr it will probably be done using a provider, with nuget being the default provider. There is no design except in my head. I mention this so you don't all hate on me for how awful the command line will be for a while :-)
b. Existing TypeProviders all target the desktop .. The inbox TP's have not been ... and will probably not be ported to coreclr. Also we have not identified a binding mechanism for allowing tp's and the compiler to agree on type loading. Lots of that is going to be changed due to coreclr limitations.
c. Environment.Exit() is not yet implemented on coreclr ... although it is coming real soon now. Exit is important to error logging and I've impmeneted it as an exception so errors appear as uncaught exceptions for now ... forgive the crappiness of it please, It will be back to normal shortly.
d. Currently It requires the specification of default.manifest on the command line.
e. There is no debugging symbols yet
Okay lets compile something: I just used VS to make an F# console app and added hello, world to program.fs
copied the program.fs file into a sunny place too: [C:\fs_smoketest]
made this batch file, also in the sunny place:
This batch file builds program.fs to run on the coreclr
When it runs you should see this:
To build it to run against coreclr is very similar: I made a batch file c.bat which contained:
When it is run you can see this:
Let me know how you find it, feel free to raid bugs, make suggestions etc ...
For now my priority is to get it working on Linux ... and I am not even close to being a Linux aficionado, and so that is going to be fun for me.
Thanks for your interest
Kevin
The text was updated successfully, but these errors were encountered: