b98d14d400
With similar reasoning to the parent commit, as downstreams, we can't determine what $<CONFIG> generator expressions would be appropriate. Upstream would have populated the INTERFACE_INCLUDE_DIRECTORIES with config-specific generator expressions, possibly appropriate for their DEBUG_CONFIGURATIONS. In theory, if we would add include directories for a DEBUG intent, we would have to match the upstream configurations for that. Rather than attempting to discover the appropriate configurations at this time, simplify the feature instead. The use of IMPORTED targets with these commands could still be added in the future if targets would export their DEBUG_CONFIGURATIONS somehow.
23 lines
391 B
C++
23 lines
391 B
C++
|
|
#include "common.h"
|
|
#include "publicinclude.h"
|
|
#include "interfaceinclude.h"
|
|
|
|
#ifdef PRIVATEINCLUDE_DEFINE
|
|
#error Unexpected PRIVATEINCLUDE_DEFINE
|
|
#endif
|
|
|
|
#ifndef PUBLICINCLUDE_DEFINE
|
|
#error Expected PUBLICINCLUDE_DEFINE
|
|
#endif
|
|
|
|
#ifndef INTERFACEINCLUDE_DEFINE
|
|
#error Expected INTERFACEINCLUDE_DEFINE
|
|
#endif
|
|
|
|
#ifndef CURE_DEFINE
|
|
#error Expected CURE_DEFINE
|
|
#endif
|
|
|
|
int main() { return 0; }
|