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

Hey Julian, thanks for the detailed response. I’ll try to get the extra information you need.

When you build locally from clean for development, everything works?

  • That’s correct. All configurations will build without issues locally (by that I mean, just changing target in VS and hitting build)

When you build on the buildfarm from clean for development, does it fail?

  • If we build Development on it’s own, it succeeds. If we build Shipping on it’s own, it succeeds. If we kick off a build of both Development AND Shipping in the same task, the Development build fails.

When you say “try a clean build on local machine; build shipping, then build development to test the hypothesis” - do you mean to run the same BuildGraph task on the local machine that we would run on Horde, i.e. build shipping and dev in the same task. Or simply clean the workspace, build shipping, then build development?

---

We decided to experiment by creating those fully-fledged ‘DeveloperTool’ modules for our debug objects and this did actually compile without any issues. The caveat remains though, in that we have to export a lot of symbols/types we wouldn’t otherwise export to achieve this.