Revision: 847
http://svn.sourceforge.net/cegcc/?rev=847&view=rev
Author: dannybackx
Date: 2006-12-27 03:07:33 -0800 (Wed, 27 Dec 2006)
Log Message:
-----------
Document the virtual deletion stuff.
Modified Paths:
--------------
trunk/cegcc/docs/using.html
Modified: trunk/cegcc/docs/using.html
===================================================================
--- trunk/cegcc/docs/using.html 2006-12-19 00:07:47 UTC (rev 846)
+++ trunk/cegcc/docs/using.html 2006-12-27 11:07:33 UTC (rev 847)
@@ -270,5 +270,45 @@
The functions supporting the <i>long double</i> type aren't supported by Windows.
strtold is an example of that, replace it by strtod if you can.
<a href="http://msdn2.microsoft.com/en-us/library/9cx8xs15.aspx">more info ..</a>
+<h2>Apparently broken include files</h2>
+<p>
+In the MinGW environment (our arm-wince-mingw32ce target),
+some include files are meant to be missing.
+That's because the environment mimics the Windows CE platform as closely as possible.
+This can lead to unexpected situations,
+because standard C include files (some that are part of the ISO C Standard)
+will appear not to work.
+<p>
+An example of this is <i><errno.h></i> :
+this include file is part of several well document standards,
+see e.g. <A HREF="http://www.opengroup.org/onlinepubs/009695399/basedefs/errno.h.html">
+ this description by the Open Group</A>.
+This functionality is not part of Windows CE,
+so a development environment that closely mimics the platform API should not
+contain this include file or implement its contents.
+<p>
+One way to implement this is to leave <errno.h> out of our mingw implementation.
+This is not what we did.
+We do have this file, but it contains a construction which will make its use always fail.
+This is because the <errno.h> contains this
+<pre>
+#ifdef __COREDLL__
+#include_next <errno.h>
+#else /* __COREDLL__ */
+..
+</pre>
+<p>
+When you try to compile a source which includes this file,
+it'll fail.
+<p>
+Pedro says he has <i>virtually deleted</i> these files :
+they're there but you can't use them any more.
+The reason for this approach is that this type of approach might allow us to
+keep our sources in sync with the maintainers (of MinGW, in this case).
+<p>
+Note that the <i>arm-wince-cegcc</i> target has different characteristics than
+<i>arm-wince-mingw32ce</i> target.
+The <errno.h> file is an example of such a difference :
+it does exist, and works, in <i>arm-wince-cegcc<i/>.
</BODY>
</HTML>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
