uet icon indicating copy to clipboard operation
uet copied to clipboard

Following README, BUILD FAILED: Couldn't find the executable to run:

Open hobsie opened this issue 6 months ago • 4 comments

Came across the Accelerating your Unreal Engine builds with BuildGraph youtube video which led me to this repository.

Followed the readme, grabbed the windows version of uet.exe, ran uet upgrade and then as the instructions suggested, tried to run the command from the same directory as a basic .uproject that i've been doing testing with.

Log looks fine until near the end:

[info] [Compile UnrealGame Win64 Development] Initializing script modules... [info] [Compile UnrealGame Win64 Development] Total script module initialization time: 0.28 s. [info] [Compile UnrealGame Win64 Development] Using C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\MSBuild.exe [info] [Compile UnrealGame Win64 Development] Executing commands... [info] [Compile UnrealGame Win64 Development] [info] [Compile UnrealGame Win64 Development] ========== Starting: Compile UnrealGame Win64 Development ========== [info] [Compile UnrealGame Win64 Development] BUILD FAILED: Couldn't find the executable to run: [info] [Compile UnrealGame Win64 Development] while executing task <Spawn Exe="" Arguments=" internal remove-stale-precompiled-headers --engine-path "" --project-path "" --target-name "UnrealGame" --target-platform "Win64" --target-configuration "Development"" LogOutput="True" ErrorLevel="1" /> [info] [Compile UnrealGame Win64 Development] at C:\Users<user>\AppData\Local\Temp\tmpdsncxa.tmp(79) [info] [Compile UnrealGame Win64 Development] (see C:\Users<user>\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.6\Log.txt for full exception trace) [info] [Compile UnrealGame Win64 Development] AutomationTool executed for 0h 0m 0s [info] [Compile UnrealGame Win64 Development] AutomationTool exiting with ExitCode=1 (Error_Unknown) [info] [Compile UnrealGame Win64 Development] BUILD FAILED [info] Moved back existing BuildConfiguration.xml [info] [Compile UnrealGame Win64 Development] Failed [fail] One or more build jobs failed: [info] Compile UnrealGame Win64 Development = Failed

The log file listed is mostly similar but it looks like it's geting a null name for an exectuable it's trying to run

========== Starting: Compile UnrealGame Win64 Development ========== SafeFileExists =False Could not resolve app .exe

Any idea what I might be missing? Maybe some setting in the uproject itself? (It's just based on the 1st person template as part of some tests i'm doing).

Installed version of 5.6 (not source version), Win11, everything run as admin.

hobsie avatar Jul 06 '25 15:07 hobsie

Not sure what's going on there.

Can you run uet --trace build -e <engine path> and upload the full logs? Thanks.

hach-que avatar Jul 07 '25 04:07 hach-que

Thanks for getting back to me, sorry it took a while to respond, was travelling for work.

I took a quick look at the logs and it looks like something isn't handling space characters in directory paths.

using this command

uet build -e 'E:\Epic Games\UE_5.6'

In the starting AutomationTool section at the start of the log it shows this for EnginePath

-set:EnginePath=E:\Epic" "Games\UE_5.6

Then later in the log it shows this for the BuildGraph

-set:EnginePath=E:\Epic

and all the SetEnvVar values also get set to simiar e.g.

SetEnvVar Games\UE_5.6 -set:TempPath=E:\Epic

Same thing seems to happen if I run build without specifying an engine path (and use the installed version I have) and it ends up splitting "C:\Program Files\Epic Games\UE_5.6" into just "C:\Program

I've moved a source version of unreal engine to "E:\EpicGames\UE_5.6" and that seems to have fixed that issue. (having a different issue not but i'll try resolve first before posting anything)

hobsie avatar Jul 13 '25 15:07 hobsie

What happens if you run uet build -e "E:\Epic Games\UE_5.6" instead of uet build -e 'E:\Epic Games\UE_5.6'? (note the difference in quotation marks)

hach-que avatar Jul 13 '25 15:07 hach-que

Sorry I should have put that in there, seemed to get the same behaviour with both dynamic and literal quotes

hobsie avatar Jul 13 '25 15:07 hobsie