CConditionalScanner does not detect included header from a command line macro

[mwichmann]

This issue is generated as a result of investigating using the CConditionalScanner to detect dependencies when the #include uses a macro, after a Discord discussion here: https://discord.com/channels/571796279483564041/571796280146133047/998690474216927345. This base problem has actually been recorded in several past issues, including #344 #2601 #3038.

The investigation shows that if the macro is defined in the source file, like this:

#define HEADER "foo.h"
#include HEADER

then CConditionalScanner indeed produces the dependency, but if it is defined as a compiler command-line option, it is not.

env = Environment(CPPDEFINES=['HEADER=\\"foo.h\\"'])

Attaching a diff to the unit test file for the C scanner, which demonstrates this behavior (unfortunately had to make into a file type github would accept)

CTests-diff.zip

[ivankravets]

Hi @mwichmann, do you use the latest development version? It should be fixed by https://github.com/SCons/scons/commit/d9192dbf0c4380043759262147e6e06b0caf590e

[mwichmann]

Doesn't seem to be... which doesn't mean my test isn't faulty. I still get:

AssertionError: False is not true : expect ['f9.h'] != scanned []

[mwichmann]

I think this may have been fixed by #4263 - not an issue with the conditional scanner, but with the way processDefines emitted a single string-valued macro. I'll need to swing by and check in more detail, but we may be able to close this.

[mwichmann]

Okay, reran the test case attached here, it still fails, but can be made to pass by:

-        env = DummyEnvironment(CPPDEFINES=['HEADER=\\"f9.h\\"'])
+        env = DummyEnvironment(CPPDEFINES=[('HEADER', '\\"f9.h\\"')])

So there may still be a CPPDEFINES hole here.

[mwichmann]

The hole is in SCons/Scanner/C/dictifyCPPDEFINES() - it does its own processing of defines, not using the processDefines routine the rest of SCons uses, and did not deal with "NAME=VALUE" strings, either as a solo value, or as a member of a sequence. (note this problem is not related to the large CPPDEFINES refactor, it was always possible to assign a single string or a string-in-a-list to CPPDEFINES, only after type conversion is triggered might you not have those anymore). I have a patch and some additional tests.