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: CODE_OF_CONDUCT.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Project maintainers who do not follow or enforce the Code of Conduct in good fai
40
40
41
41
## Attribution
42
42
43
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
43
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
1. The `update.cmd` script adds required strong name validation skips and NGens the compiler and libraries. This requires admin privileges.
170
174
1. The compiler binaries produced are "private" and strong-named signed with a test key.
171
175
1. Some additional tools are required to build the compiler, notably `fslex.exe`, `fsyacc.exe`, `FSharp.PowerPack.Build.Tasks.dll`, `FsSrGen.exe`, `FSharp.SRGen.Build.Tasks.dll`, and the other tools found in the `lkg` directory.
172
176
1. The overall bootstrapping process executes as follows
173
-
- We first need an existing F# compiler. We use the one in the `lkg` directory. Let's assume this compiler has an `FSharp.Core.dll` with version X.
174
-
- We use this compiler to compile the source in this distribution, to produce a "proto" compiler, dropped to the `proto` directory. When run, this compiler still relies on `FSharp.Core.dll` with version X.
175
-
- We use the proto compiler to compile the source for `FSharp.Core.dll` in this distribution.
176
-
- We use the proto compiler to compile the source for `FSharp.Compiler.dll`, `fsc.exe`, `fsi.exe`, and other binaries found in this distribution.
177
+
- We first need an existing F# compiler. We use the one in the `lkg` directory. Let's assume this compiler has an `FSharp.Core.dll` with version X.
178
+
- We use this compiler to compile the source in this distribution, to produce a "proto" compiler, dropped to the `proto` directory. When run, this compiler still relies on `FSharp.Core.dll` with version X.
179
+
- We use the proto compiler to compile the source for `FSharp.Core.dll` in this distribution.
180
+
- We use the proto compiler to compile the source for `FSharp.Compiler.dll`, `fsc.exe`, `fsi.exe`, and other binaries found in this distribution.
177
181
178
-
####Updating FSComp.fs, FSComp.resx and XLF
182
+
### Updating FSComp.fs, FSComp.resx and XLF
179
183
180
184
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
181
185
@@ -185,7 +189,7 @@ If your changes involve modifying the list of language keywords in any way, (e.g
185
189
186
190
This only works on Windows/.NETStandard framework, so changing this from any other platform requires editing and syncing all of the XLF files manually.
187
191
188
-
####Configuring proxy server
192
+
### Configuring proxy server
189
193
190
194
If you are behind a proxy server, NuGet client tool must be configured to use it:
191
195
@@ -195,6 +199,6 @@ If you are behind a proxy server, NuGet client tool must be configured to use it
195
199
196
200
Where you should set proper proxy address, user name and password.
197
201
198
-
####Resources
202
+
### Resources
199
203
200
-
The primary technical guide to the core compiler code is [The F# Compiler Technical Guide](http://fsharp.github.io/2015/09/29/fsharp-compiler-guide.html). Please read and contribute to that guide.
204
+
The primary technical guide to the core compiler code is [The F# Compiler Technical Guide](https://fsharp.github.io/2015/09/29/fsharp-compiler-guide.html). Please read and contribute to that guide.
*[The F# Language Specification](https://fsharp.org/specs/language-spec/)
89
89
90
90
## License
91
91
92
92
This project is subject to the MIT License. A copy of this license is in [License.txt](License.txt).
93
93
94
94
## Code of Conduct
95
95
96
-
This project has adopted the [Contributor Covenant](http://contributor-covenant.org/) code of conduct to clarify expected behavior in our community. You can read it at [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md).
96
+
This project has adopted the [Contributor Covenant](https://contributor-covenant.org/) code of conduct to clarify expected behavior in our community. You can read it at [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md).
97
97
98
98
## Get In Touch
99
99
100
-
Members of the [F# Software Foundation](http://fsharp.org) are invited to the [FSSF Slack](http://fsharp.org/guides/slack/). You can find support from other contributors in the `#compiler` and `#editor-support` channels.
100
+
Members of the [F# Software Foundation](https://fsharp.org) are invited to the [FSSF Slack](https://fsharp.org/guides/slack/). You can find support from other contributors in the `#compiler` and `#editor-support` channels.
101
101
102
102
Additionally, you can use the `#fsharp` tag on Twitter if you have general F# questions, including about this repository. Chances are you'll get multiple responses.
103
103
104
-
## About F#
104
+
## About F\#
105
105
106
106
If you're curious about F# itself, check out these links:
107
107
108
108
*[What is F#](https://docs.microsoft.com/dotnet/fsharp/what-is-fsharp)
109
109
*[Get started with F#](https://docs.microsoft.com/dotnet/fsharp/get-started/)
Write-Host" -procdump Monitor test runs with procdump"
97
98
Write-Host" -prepareMachine Prepare machine for CI run, clean up processes after build"
98
99
Write-Host" -useGlobalNuGetCache Use global NuGet cache."
100
+
Write-Host" -noVisualStudio Only build fsc and fsi as .NET Core applications. No Visual Studio required. '-configuration', '-verbosity', '-norestore', '-rebuild' are supported."
99
101
Write-Host""
100
102
Write-Host"Command line arguments starting with '/p:' are passed through to MSBuild."
101
103
}
@@ -145,8 +147,19 @@ function Process-Arguments() {
145
147
}
146
148
147
149
functionUpdate-Arguments() {
148
-
if (-Not (Test-Path"$ArtifactsDir\Bootstrap\fsc\fsc.exe")) {
149
-
$script:bootstrap=$True
150
+
if ($script:noVisualStudio) {
151
+
$script:bootstrapTfm="netcoreapp2.1"
152
+
$script:msbuildEngine="dotnet"
153
+
}
154
+
155
+
if ($bootstrapTfm-eq"netcoreapp2.1") {
156
+
if (-Not (Test-Path"$ArtifactsDir\Bootstrap\fsc\fsc.runtimeconfig.json")) {
157
+
$script:bootstrap=$True
158
+
}
159
+
} else {
160
+
if (-Not (Test-Path"$ArtifactsDir\Bootstrap\fsc\fsc.exe") -or (Test-Path"$ArtifactsDir\Bootstrap\fsc\fsc.runtimeconfig.json")) {
161
+
$script:bootstrap=$True
162
+
}
150
163
}
151
164
}
152
165
@@ -227,10 +240,37 @@ function TestUsingNUnit([string] $testProject, [string] $targetFramework) {
0 commit comments