Re: stdint.h

[Ralf Corsepius <ralf dot corsepius at rtems dot org>]

On Mon, 2005-09-19 at 21:36 -0400, Christopher Faylor wrote:
> On Tue, Sep 20, 2005 at 02:52:24AM +0200, Ralf Corsepius wrote:
> >On Mon, 2005-09-19 at 18:02 -0400, Jeff Johnston wrote:
> >> Shaun Jackman wrote:
> >> > Could stdint.h be moved from newlib/libc/sys/rtems/include to
> >> > newlib/libc/include? It's a very useful header, and the rtems
> >> > implementation looks portable.
> >> >
> >> 
> >> Sure.  Just checked in.
> ><surprized/>
> >
> >In this case, you probably also will want to move RTEMS inttypes.h,
> >because stdint.h alone is only half of the story.
> >
> >@Corinna: I recall we discussed this generalization, several months ago,
> >but agreed upon this step to potentially interfere with Cygwin.
> >Does this cause any problems for Cygwin?
> 
> It will, at the very least, conflict with cygwin's file of the same
> name.

Let me put it this way:

* Theoretically, the RTEMS stdint.h/inttypes.h should be able to replace
Cygwin's stdint.h/inttypes.h, but I haven't checked the details nor do I
have any possibility to test (I don't have Windows nor do I use Cygwin,
except that I have and occasionally use Linux->Cygwin cross compilers).

* Technically, you probably should be able (untested) to override
generalized headers in newlib, by putting your headers into
newlib/libc/sys/cygwin/include
(RTEMS uses a similar approach to override some general newlib headers
with customized headers).

Anyway, I think my RTEMS headers should also be applicable for Cygwin,
may-be some minor changes could be necessary.

Ralf