Skip to content

Fresh clone of repository results in many compilation errors #107

Open

Description

@Cjewett

I want to investigate implementing S3 compatibility for this. As an initial stab I wanted to get this compiled and working in my local environment. I tested this about a year ago and it worked fine but since then it seems like there have been some regressions.

I wanted to outline the fixes I had to implement to get this compiling in hopes that someone more familiar with the repository can provide guidance on the correct fixes for the main branch.

dotnet_diagnostic.IDE0055.severity = error # Fix formatting

Had to change that to dotnet_diagnostic.IDE0055.severity = none # Fix formatting because there were a significant amount of errors after opening the solution.

<NoWarn>$(NoWarn);NU5104</NoWarn>

Had to update this to ignore security vulnerability errors <NoWarn>$(NoWarn);NU5104;NU1901;NU1902;NU1903</NoWarn>. There were a lot of NuGet packages being flagged for vulnerabilities and preventing compilation.

The NuGet.config (https://github.com/microsoft/MSBuildCache/blob/main/nuget.config) had to be updated because it was failing to retrieve packages.
I had to do this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="nuget" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
    <add key="msbuildcache" value="https://pkgs.dev.azure.com/msbuildcache/public/_packaging/msbuildcache/nuget/v3/index.json" />
  </packageSources>
  <packageSourceMapping>
    <clear />
    <packageSource key="nuget">
      <package pattern="*" />
    </packageSource>
    <packageSource key="msbuildcache">
      <package pattern="RocksDb*" />
      <package pattern="Microsoft.BuildXL*" />
      <package pattern="Microsoft.Windows.Debuggers*" />
    </packageSource>
  </packageSourceMapping>
</configuration>

If there is something I missed that should have prevented the need to make these changes it would be appreciated if that could be called out in the README (or maybe I missed it altogether). If these are actual errors then I'm happy to help open PRs to try and fix the issues if a repository owner has guidance on what the correct fixes are.

Activity

  1. dfederm commented on Jan 2, 2025

    @dfederm
    Member

    I am not able to repro any of these issues, nor are some other folks I've gotten to try to build the repo, and the build pipelines also don't run into these issues.

    Are you able to provide more details about what you're seeing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions