-
Notifications
You must be signed in to change notification settings - Fork 167
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
Verona Build Failing: attempting to reference a deleted function #125
Comments
Hi Nate, thanks for the report. Can you clarify which step it breaks? Perhaps pasting here all commands until you reach there? We're using VS15 2017 on our CI, and yours is 2019, so the compiler should be fine. Perhaps this is an environment issue. Have a look on our Azure pipeline script, it may help you find the right flags. |
@rengolin I was successfully able to clone the repo and build it following these steps a few weeks ago. After pulling new code today I deleted my build directory to do a new build. The rebuild failed so I started fresh by deleting the repo and cloning a new one. Steps:
|
Thanks for the info. Our CI isn't reproducing your error and I don't have the same version. While I'm trying to get it, we may be able to at least find the culprit commit. One thing you can do is a git bisect, using msbuild. If you don't have the commit that used to work, just pick a commit old enough. Since the bisect does a binary search, and we have less than 200 commits, it should make no difference, as long as the early commit builds fine. Meanwhile, looking at the errors, they all seem to be of four types, default constructors:
Both Perhaps we'll understand it more when you find which commit introduced the regression, or when I can get my hands on VS 2019. |
I observed this yesterday when I had used VS2019. I will take a look at fixing. |
Thanks Matt! I just managed to reproduce it this morning too, with the community version. |
Freshly cloned repo following build steps in docs
Versions
Os: Windows 10
cmake version 3.17.20032601-MSVC_2
Visual Studio 2019 v16.6.0
The text was updated successfully, but these errors were encountered: