Can't compile 5.4 Projects anymore, I need help.

Development Programming & Scripting C++
, , , , , , , , , , , , ,
21

For anyone, who still hasn’t solved the issue:
The only thing that helped me was to install 17.10 LTSC Professional Visual Studio version instead of latest 2022 Comunity version 17.13 with all the same components I installed before.
Visual Studio 2022 Release History | Microsoft Learn.

22

It was very helpful for me! Thank you!

23

DON’T DO THIS, FOLLOW THE INSTRUCTIONS IN MY NEXT POST BELOW INSTEAD.

We just ran into this issue for a build machine that runs multiple versions of UE, so we could not update the shared build xml - this issue has been fixed in 5.5 so we patched the old engines.

What we did was to open up:

\Unreal Engine\Engine\Source\Runtime\Core\Public\Experimental\ConcurrentLinearAllocator.h

Replaced this chunk:

#if PLATFORM_HAS_ASAN_INCLUDE
#include <sanitizer/asan_interface.h>
#if defined(__SANITIZE_ADDRESS__)
#define IS_ASAN_ENABLED 1
#elif __has_feature(address_sanitizer)
#define IS_ASAN_ENABLED 1
#else
#define IS_ASAN_ENABLED 0
#endif
#else
#define ASAN_POISON_MEMORY_REGION(addr, size) ((void)(addr), (void)(size))
#define ASAN_UNPOISON_MEMORY_REGION(addr, size) ((void)(addr), (void)(size))
#define IS_ASAN_ENABLED 0
#endif

With this from UE 5.5:

#if PLATFORM_HAS_ASAN_INCLUDE
#include <sanitizer/asan_interface.h>
#if defined(__SANITIZE_ADDRESS__)
#define IS_ASAN_ENABLED 1
#elif defined(__has_feature)
#if __has_feature(address_sanitizer)
#define IS_ASAN_ENABLED 1
#else
#define IS_ASAN_ENABLED 0
#endif
#else
#define IS_ASAN_ENABLED 0
#endif
#else
#define ASAN_POISON_MEMORY_REGION(addr, size) ((void)(addr), (void)(size))
#define ASAN_UNPOISON_MEMORY_REGION(addr, size) ((void)(addr), (void)(size))
#define IS_ASAN_ENABLED 0
#endif

The key difference is that it checks defined(__has_feature)

2 Likes
24

OK - It took 2 hours and then we ran into additional issues with compiling using newer build tools.

We found a better solution:

  1. Modify Visual Studio 2022
  2. Go to Individual Components
  3. Add MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.36-17.6) (we used to have this one installed, but it got uninstalled when VS 2022 updated)
  4. Add an environment variable named VCToolsVersion with the value 14.36.32532 on the machine doing the builds

This will make the compiler use the correct tool chain.

This solution was good for us since we could specify the env variable on the Team City builds that compiled UE 5.3 and 5.2 projects.

You can check what versions of the tools you have installed by opening up the folder in Windows explorer and see what folders you have: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\

3 Likes
25

Thank you very much, my friend. I’ve been struggling for 2 days to fix this error. It only worked after I saw your post. It solved it right away.

Congratulations on the spot-on tip!

26

Thank you so much :sob: i’ve been struggling days to know why this happens till today…

27

Another post figured out a nice way of setting the compiler version in the BaseEngine.ini, that was very useful for me who need to switch between Unreal Engine versions a lot:

That way it does not become a global setting on the machine.