> > > src/gcc/gcc/config/arm/{wince-cegcc,mingw32}.h
> >
> > Sorry, I've been looking for them in the include files.
> > Anyhow, I don't really understand how the user is getting these macros.

I'm sorry, but I did try "arm-wince-mingw32ce-g++ -v".
I get NO flags listed.
It seems that there is a really significant difference betwwen "cegcc" and
"mingw32ce" compilers.
Now I can see that "arm-wince-cegcc-g++ -dumpspecs" produces CORRECT
result, while ""arm-wince-mingw32ce-g++ -dumpspecs" does NOT.

> >     #define __CEGCC32__ CEGCC32_VERSION(0,60,00)
> >     #define __MINGW32CE__ MINGW32CE_VERSION(0,60,00)
> >
> > Then it would be sufficient to implement the CEGCC32_VERSION and
> > MINGW32CE_VERSION macros as proposed in my last mail.
>
> I understand your point, but the gcc build system is rather complicated
> already. Introducing this into it is not something I'd like to do for
> two reasons : the complexity, and the same argument as with the include
> files (you can't keep this in sync with the original tool sources).

Yes, but today's include files just check whether these variables are
defined. They do not check the value. So, adding a value would not break
anything.
The problem with a new include file is that there is no way to test
whether it exists in advance. If one puts "#include <cegcc.h>" and the
file does not exist, one is lost.
That is why I am trying to find a solution which will be backwards
compatible - i.e. it uses an existing include file (which would then
include the cegcc.h automatically) and/or an existing macro.
A solution would be to add another macro to predefined macros.
Something like "__HAVE_VERSION__" (defined automatically by the compiler,
not by an include file). Then one could do:
        #ifdef __HAVE_VERSION__
        #include <cegcc.h>
        #endif

Jacek.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to