the nmake scan rules grok #include
in general
#include "FEATURE/foo"
triggers one of the FEATURE/% : features/%... pattern metarules in
Makerules.mk
for libast only the Makefile differentiates between private "FEATURE/foo"
and public <ast_foo.h> headers by this assertion
$(HEADERGEN) :COPY: FEATURE/$$(<:B:/$(ID)_//)
private means only libast src uses the header, public means the header is
installed in $(INSTALLROOT)/include/ast_*.h for all of ast
if "nanfloat" is private then one or more #include "FEATURE/nanfloat" lines
will suffice
if its public then add $(ID)_nanfloat.h to the HEADERGEN var value in
Makefile and use #include <ast_nanfloat.h>
handling implicit/generated includes as first order objects is one of the
big wins in ast nmake
On Thu, Nov 14, 2013 at 5:47 PM, ольга крыжановская <
[email protected]> wrote:
> I am puzzled how src/lib/libast/Makefile finds and executes the
> src/lib/libast/features/float probe.
>
> Can anyone explain, which dependency, in src/lib/libast/Makefile,
> triggers the src/lib/libast/features/float iffe probe?
>
> How can I add a new probe ("nanfloat") which should be executed the
> same way, and with the same dependencies, as
> src/lib/libast/features/float?
>
> Olga
> --
> , _ _ ,
> { \/`o;====- Olga Kryzhanovska -====;o`\/ }
> .----'-/`-/ [email protected] \-`\-'----.
> `'-..-| / http://twitter.com/fleyta \ |-..-'`
> /\/\ Solaris/BSD//C/C++ programmer /\/\
> `--` `--`
>
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
