You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,8 +68,6 @@ Contributions to this repository will be rigorously policed for quality.
68
68
69
69
All code submissions should be submitted with regression test cases, and will be subject to peer review by the community and Microsoft. The bar for contributions will be high. This will result in a higher-quality, more stable product.
70
70
71
-
- We expect contributors to be actively involved in quality assurance.
72
-
- We expect contributors to be actively involved in quality assurance.
73
71
- We expect contributors to be actively involved in quality assurance.
74
72
- Partial, incomplete, or poorly-tested contributions will not be accepted.
75
73
- Contributions may be put on hold according to stability, testing, and design-coherence requirements.
Before running the build scripts, ensure that you have cleaned up the visualfsharp repo by running this git command:
10
+
11
+
git clean -xfd
12
+
13
+
This will remove any files that are not under version control. This is necessary only if you have already attempted to build the solution or have made other changes that might prevent it from building.
14
+
15
+
##Installing Dependencies and Building
16
+
3
17
Follow the instructions below to build and develop the F# Compiler, Core Library and tools on Windows, macOS and Linux.
4
18
5
19
-[Developing the F# Compiler (Windows)](#developing-the-f-compiler-windows)
@@ -20,10 +34,6 @@ Install
20
34
21
35
2. The command prompt must have Administrator rights (`Run as Administrator`).
22
36
23
-
Before running the build scripts, ensure that you have cleaned up the visualfsharp repo by running this git command:
24
-
25
-
git clean -xfd
26
-
27
37
On Windows you can build the F# compiler for .NET Framework as follows:
28
38
29
39
build.cmd
@@ -120,7 +130,8 @@ Testing the .NET Core version of the F# compiler on macOS and Linux is TBD.
120
130
121
131
To build and test Visual F# IDE Tools, install these requirements:
122
132
123
-
-[Visual Studio 2017](https://www.visualstudio.com/downloads/)
133
+
- Download[Visual Studio 2017](https://www.visualstudio.com/downloads/)
134
+
- Launch the Visual Studio Installer
124
135
- Under the "Windows" workloads, select ".NET desktop development"
125
136
- Select "F# desktop language support" under the optional components
126
137
- Under the "Other Toolsets" workloads, select "Visual Studio extension development"
@@ -195,7 +206,11 @@ For **Release**:
195
206
196
207
vsintegration\update-vsintegration.cmd release
197
208
198
-
#Notes
209
+
##Debugging the F# Compiler
210
+
211
+
See the "Debugging The Compiler" section of this[article](https://medium.com/@willie.tetlow/f-mentorship-week-1-36f51d3812d4)
212
+
213
+
##Notes
199
214
200
215
####Windows: Links to Additional frameworks
201
216
@@ -223,15 +238,16 @@ To do this, build the non-buildfromsource version of FSharp.Compiler.Private (sr
If your changes involve modifying the list of language keywords in any way, (e.g. when implementing a new keyword), the XLF localization files need to be synced with the corresponding resx files. This can be done automatically by running
This only works on Windows/.NETStandard framework, so changing this from any other platform requires editing and syncing all of the XLF files manually.
234
249
250
+
You can also change build.cmd to default COPY_FSCOMP_RESOURCE_FOR_BUILD_FROM_SOURCES to 1 under ":ARGUMENTS_OK" label.