Thanks
To follow-up on this, something I’ve also noticed is that IsPluginCompiledForTarget() creates its own local argument for bBuildDeveloperTools, meaning that if your build target overrides this flag, IsPluginCompiledForTarget() will fail regardless.
Our use-case is that we want to include developer tools in test builds.
We’re also looking into the AdditionalDependencies field for ModuleDescriptor. The comment claims that this field can specify other modules which are required in order to build/include this module, but in practice that field doesn’t seem to be used anywhere within the build system. Can somebody confirm whether this is feasible to use or not?
We essentially want certain project-level plugin modules to conditionally compile, based on the presence/enabled state of another plugin.