Horde fails multi-configuration build task when using ConditionalAddModuleDirectory() to compile optional files.

Hey there,

No worries - happy to help as best I can here.

>If we kick off a build of both Development AND Shipping in the same task

  • Specifically, do you have the buildgraph fragment that is issued here? Ordering will really matter here. What I’m thinking is that Shipping builds first - doesn’t emit the necessary UHT; Development runs after; intermediates (not compilation units; things like makefiles or UHT metadata) signal that we don’t need to run UHT for your circumstance; we end up with error.

I mean quite literally just issuing two calls, back to back on a clean. So:

  • dotnet UNrealBuildTool.dll -Target=“TARGETNAME Win64 Shipping” -Clean
  • dotnet UNrealBuildTool.dll -Target=“TARGETNAME Win64 Development” -Clean
  • dotnet TARGETNAME Win64 Shipping
  • dotnet TARGETNAME Win64 Development

At this point, I think we are trying to track down exactly what files are not being explicitly generated. My hunch is that the above will fail for local user as well. Again the build graph details matter a lot for the build farm case where you’re observing both dev and shipping on same ‘task’ resulting in dev build failure.

Kind regards,

Julian