Installed Build is too large

Development Platform & Builds
, , , , , ,
1

I compiled the Installed Build Engine from source code of UE5.1 using the following command:

Engine\Build\BatchFiles\RunUAT.bat BuildGraph -target="Make Installed Build Win64" -script=Engine/Build/InstalledEngineBuild.xml -set:WithMac=false -set:WithMacArm64=false -set:WithAndroid=false -set:WithIOS=false -set:WithTVOS=false -set:WithLinux=false -set:WithLinuxArm64=false -set:WithHTML5=false -set:WithSwitch=false -WithDDC=false -set:WithWin32=false -set:WithLumin=false -set:WithPS4=false -set:WithXboxOne=false -set:WithHoloLens=false -set:GameConfigurations=Shipping

I’ve tried different -set:GameConfigurations settings, but they all result in about 90GB, which is far more than the official 30GB:

GCFEN`T2N~50M0HFNY~~{4
GCFEN`T2N~50M0HFNY~~{4539Ă—721 10.2 KB

I compared the engine files of the Epic launcher and found that there are many more large binary files:

image
image1501Ă—1954 500 KB

image
image1501Ă—1954 443 KB

image
image1501Ă—1954 400 KB

FolderComparison.txt (423.0 KB)

This problem has been going on for a long time in different engine versions. The newer the version, the bigger the Installed Build is, which is not conducive to release.
How can I compile the Installed Build Engine with the same size as the official version?

1 Like
2

Well, the solution is to delete all “.pdb” files:

@echo off
setlocal enabledelayedexpansion

set target_directory=LocalBuilds

for /r "%target_directory%" %%f in (*.pdb) do (
    echo Deleting "%%f"
    del "%%f"
)

echo All .pdb files in "%target_directory%" have been deleted.

endlocal

After deletion, the package size is less than 30GB, which means that the engine does not contain debug info, and cannot package C++ games, but it is very suitable for distribution to artists

2 Likes
3

Hi, when we compile the installed build engine from source code of UE5.1, how do we prevent the generation of pdb files ??

4

I’m not sure, it may not be possible to prevent the .pdb file from being generated, I can only delete it through the .bat script mentioned above

5

I haven’t tried it, but per the docs here, if you pass the argument -set:WithFullDebugInfo=false it should prevent .pdb files from being included in the Installed Build.

6

Just tried my previous post, seems that even with -set:WithFullDebugInfo=false it still includes .pdb files in the generated LocalBuilds folder :frowning:

7

thanks

8

The official version remains some pdb files and can package c++ games. So are these pdb files minimal requirements? Why? Are there any relevant documents and instructions?

9

I have a solution that can package Project. The way is to open the unreal editor and search the engine fold to find the .pdb files , then manual delete them . When the system warrning you that the file is being used then just skip all. Finally you will get a small engine and can package!

10

The Solution is very simple .
Open the file Engine/Build/InstalledEngineFilters.xml

Find the line that start with…

       <!-- Content -->
	Engine/Content/....psd
	Engine/Content/....pdn
	Engine/Content/....po

and add at the end…

Engine/Binaries/*/…pdb
Engine/Plugins/…pdb

So the whole line will be…

     <!-- Content -->
	Engine/Content/....psd
	Engine/Content/....pdn
	Engine/Content/....po
    Engine/Binaries/*/....pdb
    Engine/Plugins/....pdb
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.