Skip to content

Build doesn't work on Linux? #103

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

Open
IanWitham opened this issue Apr 13, 2025 · 4 comments
Open

Build doesn't work on Linux? #103

IanWitham opened this issue Apr 13, 2025 · 4 comments

Comments

@IanWitham
Copy link

IanWitham commented Apr 13, 2025

The build instructions work for me on Windows but I can't get the docs to build on Linux. I'm doing the obvious things like changing the path separators.

FSDocs can't find any namespaces, so no API docs are produced.

Is this expected, or am I missing something?

@dsyme
Copy link
Contributor

dsyme commented Apr 13, 2025

@IanWitham
Copy link
Author

IanWitham commented Apr 13, 2025

The CI matches the build steps in the readme. I notice the CI is configured to run on Windows.

I did get it to work by running Build.sh. This takes a long time and seems to build multiple versions. I don't fully understand the magic that's happening with the fsproj in this repo, which I'm guessing helps to do a more targeted build.

@nojaf
Copy link
Collaborator

nojaf commented Apr 13, 2025

So, your problem is with building the F# compiler?
Might be worth listed the output where things are going wrong.

@IanWitham
Copy link
Author

The F# compiler build seems to work and has the same output on both Windows and Linux.

$ dotnet build src/FSharp.Core/FSharp.Core.fsproj /p:BUILDING_USING_DOTNET=true
Restore complete (1.0s)
  FSharp.Core netstandard2.0 succeeded (0.2s) → artifacts/bin/FSharp.Core/Debug/netstandard2.0/FSharp.Core.dll
  FSharp.Core netstandard2.1 succeeded (0.3s) → artifacts/bin/FSharp.Core/Debug/netstandard2.1/FSharp.Core.dll

I managed to get the fsdocs to build only after changing the TargetPaths in FSharp.Core.fsproj from Release to Debug, otherwise it complains that it can't find DLLs under the Release path.

The weird thing to me is that on Windows it also builds the DLLs to Debug paths, yet the FsDocs build works in that case with the same "Release" path in the fsproj.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants