assuming gcc is the mingw cc on $PATH ...
the preprocessor is run-time configurable
usually from probe information in the file named by
probe -k C pp gcc
listed by
probe -l C pp gcc
if you call cpp standalone (outside of the uwin cc wrapper)
then you must tell it what cc it should mimic with this option
-D-Xgcc
otherwise it will mimic the default cc
if the probe info for gcc does not exist then it should
be automatically generated -- this stderr message is printed
before the automatic (re)probe
probing C language processor <path-of-cc> for pp information
for gcc you should see this pragma in the probe -l output
#pragma pp:headerexpand
with this pragma your example should work
before generating the probe info you can try this to verify
cpp -D:headerexpand ...
On Thu, 05 Nov 2009 16:33:15 -0600 [email protected] wrote:
> This is my first time using UWIN.
> I installed
> uwin-base.2009-11-02.win32.i386.exe
> and
> uwin-dev.2009-11-02.win32.i386.exe
> into directory C:\Program Files\UWIN
> and have installed MinGW into directory C:\MinGW
> I seem to of found a problem with your preprocessor
> #define JACOB .
> #define HI(name) <JACOB/std##name>
> #warning HI(io.h)
> #include HI(io.h)
> should properly #include the <./stdio.h> header,
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
