On Thu, 2007-11-15 at 18:40 +0100, Jacek M. Holeczek wrote:
> > > I'm OK with releasing a 0.6.  I don't think we have any show
> > > stoppers.
> 
> I've got yet another stupid question.

Not a stupid one.

> Is there any macro implemented, which I can test in the source code, that
> says what version the CeGCC is it?

No, but usually this is a good idea. Unless Pedro is wildly opposed to
the idea, I am willing to implement this.


> The point is, one needs a way to make the source code aware of "CeGCC
> problems", which are "CeGCC version" dependent.
> The "doc" mentions __CEGCC__ and __CEGCC32__, but I couldn't find any
> place where they are defined.

src/gcc/gcc/config/arm/{wince-cegcc,mingw32}.h

I don't feel like adapting one of the standard include files for this, I
propose to create an additional include file, only present in our
distributions, that would be generated automatically by our release
scripts.

You would be able to use it as
        #if defined(__CEGCC__) || defined(__MINGW32CE__)
        #include <cegcc.h>
        #endif

and then do your thing with the macro's supplied.

How about that ?

        Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to