FSharp does not produce all packages in source-build

It looks like recently, FSharp split its build into two solutions: FSharp.sln, which contains most of the projects, and Microsoft.FSharp.Compiler.sln, which seems to only package the files produced by FSharp.sln. I’m looking at https://github.com/dotnet/fsharp/pull/12628

In source build, we were previously building only FSharp.sln which produced all of the packages we needed. However now we are missing Microsoft.Fsharp.Compiler.nupkg when we build only FSharp.sln, which is expected given the changes.

We have tried to produce both solutions with the following syntax in SourceBuild.props:

<InnerBuildArgs>$(InnerBuildArgs) '/p:Projects="$(InnerSourceBuildRepoRoot)\FSharp.sln;$(InnerSourceBuildRepoRoot)\Microsoft.FSharp.Compiler.sln;"'</InnerBuildArgs>

The problem here is that these solutions end up building concurrently even though they depend on each other. Microsoft.FSharp.Compiler is looking for fsc.dll before FSharp is finished producing it.

How should this dependency be managed, and how does the Microsoft build of fsharp work today? Do the two solutions need to build separately, one after the other? Are there any simple changes that we could make to solve this problem for source build?

@KevinRansom @crummel @MichaelSimons

see also https://github.com/dotnet/source-build/issues/2873

[KevinRansom]

@MichaelSimons , okay I have a fix, that should work well for you.

[vzarytovskii]

@MichaelSimons I will fix it.