Skip to content
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

Cannot build fornax repo for PR #105

Closed
Freymaurer opened this issue Apr 1, 2022 · 5 comments · Fixed by #112
Closed

Cannot build fornax repo for PR #105

Freymaurer opened this issue Apr 1, 2022 · 5 comments · Fixed by #112

Comments

@Freymaurer
Copy link
Contributor

Freymaurer commented Apr 1, 2022

Describe the bug
Hey i am currently working on a PR to fix #104 but i can't build fornax following the steps in the README.md:

To Reproduce

Build process

  • You need .NET Core 5.0 SDK
  • Run dotnet tool restore to restore the .NET 5 local tools defined at .config/dotnet-tools.json
  • To build the project run dotnet fake build

Error:

There was a problem while setting up the environment:
-> Could not find referenced assemblies in path: 'C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.0\ref\net6.0', please check installed SDK and runtime versions

Expected behaviour
Fornax builds.

Environment (please complete the following information):

dotnet --list-sdks

3.1.413 [C:\Program Files\dotnet\sdk]
5.0.406 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]
6.0.201 [C:\Program Files\dotnet\sdk]

dotnet --info

.NET SDK (reflecting any global.json):
 Version:   6.0.101
 Commit:    ef49f6213a

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19043
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.101\

Host (useful for support):
  Version: 6.0.3
  Commit:  c24d9a9c91

.NET SDKs installed:
  3.1.413 [C:\Program Files\dotnet\sdk]
  5.0.406 [C:\Program Files\dotnet\sdk]
  6.0.101 [C:\Program Files\dotnet\sdk]
  6.0.201 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.19 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.23 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Seems to be an issue with the build.fsx, but i have no idea how to adress this.

Pretty sure i encountered it already in other projects which i then upgraded to use a build.fsproj to circumvent this.

@baronfel

@baronfel
Copy link
Contributor

baronfel commented Apr 1, 2022

can you try updating the fake-cli dotnet tool from the current 5.21 alpha to 5.22.0 and see if that resolves the issue?

@baronfel
Copy link
Contributor

baronfel commented Apr 1, 2022

Otherwise, FAKE isn't doing anything incredibly complex, so a simple dotnet build should work for you.

@Freymaurer
Copy link
Contributor Author

Hey thanks for the fast reply! But I tried that already:

  1. I changed the version in dotnet-tools.json
  2. delete .fake folder
  3. dotnet tool restore
  4. retry dotnet fake build

Same error as before.

@Freymaurer
Copy link
Contributor Author

Otherwise, FAKE isn't doing anything incredibly complex, so a simple dotnet build should work for you.

Ah, yeah i get what you mean. Skip FAKE and use the commands directly, yeah that actually works. Pretty dumb to not think of that myself 😞

@rdipardo
Copy link
Contributor

rdipardo commented Apr 1, 2022

Identical problem on Linux: #103 (comment)

can you try updating the fake-cli dotnet tool from the current 5.21 alpha to 5.22.0 and see if that resolves the issue?

For reference, it does not. The targeting pack must be at the exact path, and be the exact version that fake-cli is looking for:

 'C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.0\ref\net6.0', please check installed SDK and runtime versions

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

Successfully merging a pull request may close this issue.

3 participants