Project no longer builds

IT fails with this error:
10>C:\Program Files\Unreal Engine - CSS\Engine\Source\Runtime\Core\Public\Experimental\ConcurrentLinearAllocator.h(31): Error C4668 : '__has_feature' is not defined as a preprocessor macro, replacing with '0' for '#if/#elif'
10>C:\Program Files\Unreal Engine - CSS\Engine\Source\Runtime\Core\Public\Experimental\ConcurrentLinearAllocator.h(31): Error C4067 : unexpected tokens following preprocessor directive - expected a newline
10>C:\Program Files\Unreal Engine - CSS\Engine\Source\Runtime\Core\Public\Experimental\ConcurrentLinearAllocator.h(31): Error C4668 : '__has_feature' is not defined as a preprocessor macro, replacing with '0' for '#if/#elif'
10>C:\Program Files\Unreal Engine - CSS\Engine\Source\Runtime\Core\Public\Experimental\ConcurrentLinearAllocator.h(31): Error C4067 : unexpected tokens following preprocessor directive - expected a newline
Solution:
If the one in the docs doesn't have support anymore, use v14.36-17.6
Jump to solution
26 Replies
Marcio Neves
Marcio NevesOP18h ago
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
Phenakist
Phenakist17h ago
opened up my file to see what it says, this is how mine looks; is yours the same still?
No description
Phenakist
Phenakist17h ago
if it's not the code directly, it might be a mutlithreading issue that's using the __has_feature
Rex
Rex17h ago
__has_feature is a macro, it is evaluated before compiling Question is, it shouldn't be missing unless something got garbled
Marcio Neves
Marcio NevesOP17h ago
I am also getting a _MSC_VER version warning, stating it is above the maximum supported version 🤔
Marcio Neves
Marcio NevesOP17h ago
The header is the same. And the header that issues the version warning
No description
No description
Marcio Neves
Marcio NevesOP17h ago
I wish I knew what have changed for that, other than the compiler itself 🤷🏽‍♂️
Rex
Rex17h ago
The compiler itself can be a problem tbh Is there a reason to upgrade MSVC?
Phenakist
Phenakist17h ago
what version of VS2022 are you guys running, maybe its a VS ver issue instead?
Rex
Rex17h ago
I don't remember but I don't have this issue
Phenakist
Phenakist17h ago
same, so curious if that is the link
Marcio Neves
Marcio NevesOP15h ago
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
Marcio Neves
Marcio NevesOP15h ago
17.12.0. It upgraded this week
No description
Marcio Neves
Marcio NevesOP14h ago
how have you this selected?
No description
Rex
Rex14h ago
Because the docs say to use a specific version
Solution
Rex
Rex14h ago
If the one in the docs doesn't have support anymore, use v14.36-17.6
Marcio Neves
Marcio NevesOP14h ago
Trying to enable over here seens to have solved it it is going farther them it did until last time
Rex
Rex14h ago
That's the version I use so it should work
Marcio Neves
Marcio NevesOP14h ago
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
Marcio Neves
Marcio NevesOP14h ago
That's true. I overlooked it because it was "working just fine" the way it was
Rex
Rex14h ago
Glad it's sorted out now!
Marcio Neves
Marcio NevesOP14h ago
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?
Marcio Neves
Marcio NevesOP14h ago
I tried building the entire solution, it recreated some of the dll, but not all, many fail due to security issues 😑
No description
Rex
Rex13h ago
Hmmm, are you using VS 2022 Community or some preview/beta version?
Marcio Neves
Marcio NevesOP13h ago
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
Marcio Neves
Marcio NevesOP13h ago
Well, that did it. Adding the warning as <WarningsNotAsErrors> did not change anything, but that did. Alpakit is working now
No description
Want results from more Discord servers?
Add your server