5.4 source build errors

[JoeBlo]

Appologies if this didn’t land in the right area. Has anyone else encountered this when trying to build the release UE5.4 from source? If so, any insights?

96>[1/2] Link [x64] CmdLink.exe
96>Module.Core.11.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.14.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.3.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.8.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.9.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.10.cpp.obj : error LNK2001: unresolved external symbol “wchar_t * GInternalProjectName” (?GInternalProjectName@@3PA_WA)
96>Module.Core.3.cpp.obj : error LNK2001: unresolved external symbol “wchar_t const * const GForeignEngineDir” (?GForeignEngineDir@@3PEB_WEB)
96>…\Binaries\Win64\CmdLink.exe : fatal error LNK1120: 2 unresolved externals

[SourDumplings]

Got same problem

[render.everything]

Getting the same

[monstercoo]

I’m also hitting this after integrating 5.4.1

[IMGGustav]

Same here, I tried changing Visual Studios build tools as stated in the known issues:

Known Issue:

Compiling Microsoft platforms with the Visual Studio 2022 “MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.39-17.9)” toolchain will cause internal compiler errors.

Workaround:

In the Visual Studio 2022 installer, install the “MSVC v143 - VS 2022 C++ x64/x86 build tools (v14.38-17.8)” individual component before compiling.

But no luck

[IMGGustav]

Hey all, I got it working, remove the CdmLine program from the solution. Compiles fine. But you wont get CmdLine anymore obviously. But if you dont need it, this works at least.

[monstercoo]

Fwiw, I’m on the same MSVC and can compile, but will occasionally hit the issue. I’ve noticed that it seems to happen when I select “Build Solution” in Visual Studio 2022, but if I right click my game’s project and select “Build,” the build will succeed.

I’m convinced this is a visual studio issue.

[JoeBlo]

I’ve heard that building the engine for a particular project will work, but building the engine standalone (which is what I am trying to do), seems to fail with those globals not being found during the link stage.

Is it possible those missing globals are only around when a project is present. For now, I have fallen back to UE5.3 source build. It compiles just fine. Will port my project over when the 5.4 build issues is solved.

I was just looking forward to the new animation retargeting in 5.4

[bazilio_113]

I think i fixed it:

Open CmdLink.cpp

add after line:
include “Windows/WindowsPlatformNamedPipe.h”

this code:
#if IS_PROGRAM
TCHAR GInternalProjectName[64] = TEXT( “CmdLink” );
const TCHAR *GForeignEngineDir = nullptr;
#endif

[JoeBlo]

This worked for me. Was able to create a client server app with it, and that is what I was looking to do.