You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to update vcpkg using the bootstrapping option, but ultimately wasn't able to get NVTT port to build, getting internal compiler errors from MSVC (possibly something on their side, that might be fixed in the future). I wasn't able to use the official NVTT port either since it brought some new dependencies with it, that themselves didn't seem to work properly with our setup.
Relevant PRs: #1606 - Initial fix that worked briefly. #1611#1613 - A couple of failed attempts to fix NVTT. #1616 - Giving up and downgrading the environment. #1633 - Reverting previous changes as they broke the aarch64 build.
The build worked for a brief period of time after enabling bootstrapping with #1606 https://github.com/vircadia/vircadia/runs/5274016300?check_suite_focus=true (Windows Server 2022, Visual Studio 17 2022)
and that's why the PR was merged, but then it started failing again I'm guessing due to another environment update.
The text was updated successfully, but these errors were encountered:
I had to update vcpkg using the bootstrapping option, but ultimately wasn't able to get NVTT port to build, getting internal compiler errors from MSVC (possibly something on their side, that might be fixed in the future). I wasn't able to use the official NVTT port either since it brought some new dependencies with it, that themselves didn't seem to work properly with our setup.
Relevant PRs:
#1606 - Initial fix that worked briefly.
#1611 #1613 - A couple of failed attempts to fix NVTT.
#1616 - Giving up and downgrading the environment.
#1633 - Reverting previous changes as they broke the aarch64 build.
The build worked for a brief period of time after enabling bootstrapping with #1606
https://github.com/vircadia/vircadia/runs/5274016300?check_suite_focus=true (Windows Server 2022, Visual Studio 17 2022)
and that's why the PR was merged, but then it started failing again I'm guessing due to another environment update.
The text was updated successfully, but these errors were encountered: