I am facing a bizarre issue with the build. Two copies of the repo, each at commit 6096b5e, one builds and the other fails.

I have some minor contributions I'd like to make, and towards that goal I'm trying to get in a state where I can reliably build the solution. I am having difficulties that I cannot explain, and I am at a loss to even speculate as to the reasons.

I cloned the repo about March 31st, that repo is at commit 6096b5e. It builds fine, with no obvious errors, and searching for "-- FAILED" in the build output finds nothing. I made my quite minor proof-of-concept modifications, rebuilt it and it ran fine and as expected.

I then had the idea to re-clone the repo to get things into a more up-to-date state, and redo my changes with the aim of preparing a pull request. But I could not get it to build at all.

I was glad that I kept my previous version of the tree intact, because at least that is still working.

I decided to investigate by creating a new worktree for the repo, and checking out commit 6096b5e into that folder. I then attempted to "Rebuild all".

Quite a few failures, indicating missing dependencies/references. I will of course include the full build output, because I don't know exactly which details will turn out to be important.

I did create a script which did git ls-files and verified that the files in both trees were identical using Get-FileHash, out an abundance of caution. But this only counts for the source files, it turns out that there are differences in some folders when I compare with Beyond Compare.

Most concerning is that the vcpkg_installed folders contain libraries that are not identical.

Start by comparing the two worktrees at commit 6096b5e, including their vcpkg_installed folders and the reported build output. Determine why identical tracked source files produce different dependency or reference failures, then verify that the same checkout can complete a rebuild reliably.