Project no longer builds
IT fails with this error:
38 Replies
Does anyone know why? It was building fine last I tried. Some VS update break it?
It may be a precompiled stuff. Trying a clean rebuild
No deal, same error. I saw another topic from a month ago about it, but no clear solution
opened up my file to see what it says, this is how mine looks; is yours the same still?
if it's not the code directly, it might be a mutlithreading issue that's using the __has_feature
__has_feature is a macro, it is evaluated before compiling
Question is, it shouldn't be missing unless something got garbledI am also getting a _MSC_VER version warning, stating it is above the maximum supported version 🤔
The header is the same. And the header that issues the version warning
I wish I knew what have changed for that, other than the compiler itself 🤷🏽♂️
The compiler itself can be a problem tbh
Is there a reason to upgrade MSVC?
what version of VS2022 are you guys running, maybe its a VS ver issue instead?
I don't remember but I don't have this issue
same, so curious if that is the link
Why wouldn't I? It is also my working machine, having the latest security patches and fixes is quite a rule. I use Rider, but it runs the VS2022 toolsets
17.12.0. It upgraded this week
how have you this selected?
Because the docs say to use a specific version
Solution
If the one in the docs doesn't have support anymore, use v14.36-17.6
Trying to enable over here
seens to have solved it
it is going farther them it did until last time
That's the version I use so it should work
it is building just fine, warnings aside
it is also no longer complaninig about compiler version
So, it must be removing the toolset for the latest one at each update. Since it was already building I never checked the specific toolset version to be enabled in the installer
all done. Thanks for the help
That's true. I overlooked it because it was "working just fine" the way it was
Glad it's sorted out now!
And being "out of support" just mean they will no longer be worked on for fixes, but they should still work regardless
And NOW my AutomationTool.dll just vanished 😑
should I reinstall and reintegrate wwise all over again, from scratch?
I tried building the entire solution, it recreated some of the dll, but not all, many fail due to security issues 😑
Hmmm, are you using VS 2022 Community or some preview/beta version?
Professional. But I get what is happening, I did a Clean solution, and it deleted the recompiled dlls that come with the setup. And due to that warnings treating as erros, it refuses to build them back
Well, that did it. Adding the warning as <WarningsNotAsErrors> did not change anything, but that did. Alpakit is working now
do the docs need to be updated with new version numbers of something?
I think the docs currently say 14.34 and the vsconfig file also says 14.34
Ideally, one would bump the MSVC version to 14.36 everywhere
I have
v14.36-17.6 because VS told me v14.34-17.4 was out of support or something. VS suggested installing the latest MSVC version, but my gut feelings told me to use the closest version that was not out of support (v14.36-17.6)
But I remember seeing at least another case of someone installing the latest version, so I'd suggest adding a note in the docs@Mircea did you have to mess with these at all to get the project building after the recent header update?
Nope, haven't touched VS settings since first installing it
I'm not sure but I think this happened to people using another edition of VS2022 (community preview or professional)
Doesn't seem to be out of support
.5 is out of support, looks like even numbers are LTS
I mean, it isn't for me right now
I don't know why I got that warning back when I did the 1.0 setup