Could different compilers use different Intermediate directories?

Development Pipeline & Plugins
, ,
1

I’m wondering how difficult it would be to use a different Intermediate directory when switching between compilers on the same platform. For example, if I want to compile for Win64 with MSVC and then with clang (because it detects different/more issues), the clang build will blow away my MSVC build products, and the next MSVC build will be a full compile. We often do nonunity builds as well, and it’s nice that those go in the NU suffix folder. I realize these are controlled by UnrealIntermediateEnvironment and UEBuildTarget.GetTargetIntermediateFolderName/GetPlatformIntermediateFolder, so I’m not proposing adding a new intermediate environment per compiler. But in the same way that was extended for multiple PC architectures, it would be nice if it could be extended for multiple compilers.

[Attachment Removed]

2

It’s possible but we don’t have any plans to do so at the moment. Something you could do is make a separate target.cs that derives from your primary target and set that to build with clang, and that will use a different named intermediate directory since the target name is different.

[Attachment Removed]