TargetLinkType.Monolithic vs TargetLinkType.Modular for Cooked Editor

Development Pipeline & Plugins
, ,
1

Hi Epic,

When generating cooked unreal editor as per documentation we are invoking SetDefaultsForCookedEditor which sets the link type to monolithic. I also noticed this is what leads to ensuring cooked editor mounts paks during launch from this code path : IPlatformFilePak.cpp

#if (!WITH_EDITOR || IS_MONOLITHIC || UE_FORCE_USE_PAKS)
    if (!FParse::Param(CmdLine, TEXT("NoPak")))
    {
        #if UE_FORCE_USE_PAKS
            Result = true;
        #else
            Result = CheckIfPakFilesExist(Inner, PakFolders);
        #endif
    }
#endif

I am running into this issue :

LINK : fatal error LNK1140: limit exceeded for program database; link with /PDB:NONE

Which I am able to bypass by setting

LinkType = TargetLinkType.Modular;

GlobalDefinitions.Add(“UE_FORCE_USE_PAKS=1”);

WindowsPlatform.PdbPageSize = 32768;

I want to know if there are inherent risks of using modular linking over monolithic? are there any other gotchas as a result.

Thank you.

Kind Regards,

Abhi

2

Hello!

There should be no risk in using that mode. The main downside of using modular linking is that the startup time of editor will be increased.

Regards,

Martin