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
378 B
C++
23 lines
378 B
C++
|
|
#ifdef MY_PRIVATE_DEFINE
|
|
#error Unexpected MY_PRIVATE_DEFINE
|
|
#endif
|
|
|
|
#ifndef MY_PUBLIC_DEFINE
|
|
#error Expected MY_PUBLIC_DEFINE
|
|
#endif
|
|
|
|
#ifndef MY_INTERFACE_DEFINE
|
|
#error Expected MY_INTERFACE_DEFINE
|
|
#endif
|
|
|
|
#ifdef SHOULD_NOT_BE_DEFINED
|
|
#error Unexpected SHOULD_NOT_BE_DEFINED
|
|
#endif
|
|
|
|
#ifndef SHOULD_BE_DEFINED
|
|
#error Expected SHOULD_BE_DEFINED
|
|
#endif
|
|
|
|
int main() { return 0; }
|