[build2] How to detect and configure #define macros?

[Joshua Olson]

To generate a config.h, you have to find which macros are used in the
source code, right?

Detecting used macros would be enough for my use case, but I can imagine
code that #defines a default if not given a value by the compiler.

On Mon, Nov 6, 2017 at 8:34 AM, Boris Kolpackov <boris at codesynthesis.com>
wrote:

> Joshua Olson <0joshua.olson1 at gmail.com> writes:
>
> > That sounds like a good way to do it. Or simply a list of macro
> definitions
> > the compiler detects and where they were detected.
>
> Now I am completely lost: "list of macro definitions the compiler detects
> and where they were detected" -- what does this even mean? I've never heard
> of compilers (I presume C++ compilers) detecting macros.
>
> Boris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/users/attachments/20171106/6c92e166/attachment-0001.html>