> > I'm OK with releasing a 0.6. I don't think we have any show
> > stoppers.
I've got yet another stupid question.
Is there any macro implemented, which I can test in the source code, that
says what version the CeGCC is it?
If not, could you, please, implement it?
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.
In some kind of a CeGCC "main" include file, which is then included by
all another includes, one could put something like this:
#ifndef CEGCC_VERSION
#define CEGCC_VERSION(VERSION,SUBVERSION,PATCHLEVEL) (((VERSION) << 16)
+ ((SUBVERSION) << 8) + (PATCHLEVEL))
/* current version information automatically generated by installer*/
#define CEGCC_RELEASE "0.60/00"
#define CEGCC_RELEASE_DATE "Nov 15 2007"
#define CEGCC_RELEASE_TIME "18:01:54"
#define CEGCC_VERSION_CODE CEGCC_VERSION(0,60,00)
#endif /* CEGCC_VERSION */
Then, one could use it as:
#if CEGCC_VERSION_CODE >= CEGCC_VERSION(0,60,00)
#include <newheader.h> /* new CeGCC 0.60.0 */
#else
#include <oldheader.h> /* old CeGCC 0.50.0 */
#endif
Best regards,
Jacek.
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
