Skip to content

Commit e2782fd

Browse files
authored
Mention the DotnetFscCompilerPath property (#13874)
The very useful `DotnetFscCompilerPath` property doesn't seem to be documented anywhere. I'm not sure if there's an authoritative location for .fsproj properties, but it might be useful to mention this property in the DEVGUIDE.
1 parent 2c3ff6d commit e2782fd

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

DEVGUIDE.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,18 @@ You can find all test options as separate flags. For example `build -testAll`:
121121

122122
Running any of the above will build the latest changes and run tests against them.
123123

124+
## Using your custom compiler to build other projects
125+
126+
Building the compiler using `build.cmd` or `build.sh` will output artifacts in `artifacts\bin`.
127+
128+
To use your custom build of `Fsc`, add the `DotnetFscCompilerPath` property to your project's `.fsproj` file, adjusted to point at your local build directory, build configuration, and target framework as appropriate:
129+
130+
```xml
131+
<PropertyGroup>
132+
<DotnetFscCompilerPath>D:\Git\fsharp\artifacts\bin\fsc\Debug\net7.0\fsc.dll</DotnetFscCompilerPath>
133+
</PropertyGroup>
134+
```
135+
124136
## Updating FSComp.fs, FSComp.resx and XLF
125137

126138
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

0 commit comments

Comments
 (0)