Re: [MinGW-dvlpr] nans for libstdc++ numeric_limits (and C runtime)

>
> I agree, go for it. Beyond that though, I still think we need to draft
> an RFC white paper.
Yes.
>I've been building several packages recently since
> I released MSYS and things just go smooth. I'm now trying to build
> perl. I've a hints/mingw32.sh already created with a mingw32 default
> system selectable. Once I get it building I'll upload it as a
> mingw-contrib release. Once perl is in place then I want to add
> autoconf, automake and libtool (Chuck Wilson's devel version). With
> this supporting dll building out of the configure script will be just a
> matter of using libtool.
>
> I see us creating a Win32 package that uses a Win32 style installation.
> I'm already looking at INNO Setup to accomplish this. INNO Setup is
> written in DELPHI and is Open Source. From what I've learned so far
> it'll be a useful tool for creating a complete MSYS,GCC,runtime,w32api
> combined installation. We could even add the "Visual MinGW IDE" if we
> really wanted to. Once I get a .iss (INNO Setup Script) template setup
> for MSYS I'll upload it to CVS so that we can expand on it together.
>
Sounds like MinGW-Max (the minguin that devoured Cleveland).
> I would like to see MinGW become the best developer solution for
> Win32/64 and not just a solution.
>
Golly, when do we sleep?
Danny
> Earnie.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
http://movies.yahoo.com.au - Yahoo! Movies
- Vote for your nominees in our online Oscars pool.

--- Earnie Boyd <earnie_boyd@...> wrote: > Hmm, indeed. Perhaps we
need to expand the definition of MinGW.
> Perhaps we should enhance the definition of MinGW to allow for
> improvements that our current definition doesn't allow. The problem
> will be the whiners of pure minimalism. I've really only seen one maybe
> two of such whiners on the users list. Perhaps they could be satisfied
> with a _STRICT_MS macro perhaps we shouldn't care. If we can provide a
> better product than MS while still using their runtime why not.
>
> To add more fuel, MS has now introduced CLR which isn't a bad thing but
> we'll soon be seeing requests for support on the users list. Corinna
> has begun to add support to Cygwin for 64 bit structures. Perhaps we
> need to do the same for MinGW.
>
> I think it's time we take a look at the future direction of MinGW as
> developers first, creating a white paper and then submitting an RFC to
> the users list. Comments?
>
> Earnie.
Yes, a lot but I'll keep it short until I actually deliver something
concrete to look at, as an addition to mingw-runtime package
I would like to have a library called libmingwex.a which contains:
1) what is now in libisocext.a
2) a few more C99 math functions that will be declared in math.h (fp
classification functions and macros) and new C99 header fenv.h (get/set fpu
environ, rounding mode, fp exception trapping)
3} The nan business which is related to (2)
4) dirent
5) a home for other POSIXisms. First on the list is gettimeofday.
6) a home for other C99isms.
7) Mumits' mingw_fseek that covers some of the deficiencies of W9x fseek
This lib would become a system lib, automatically put into search list by
specs. Many of the functions are needed for more complete libstdc++
support, so I would like them to be available by default.
In headers, the extras could be guarded by
#ifndef __NO_ISIOCEXT
or
#ifndef __NO_POSIXEXT
or both
but they would all live together in the same lib.
This would be ready for and become implemented with pre-release of 3.1
Danny
http://movies.yahoo.com.au - Yahoo! Movies
- Vote for your nominees in our online Oscars pool.

Danny Smith wrote:
>
> Yes, a lot but I'll keep it short until I actually deliver something
> concrete to look at, as an addition to mingw-runtime package
>
> I would like to have a library called libmingwex.a which contains:
> 1) what is now in libisocext.a
> 2) a few more C99 math functions that will be declared in math.h (fp
> classification functions and macros) and new C99 header fenv.h (get/set fpu
> environ, rounding mode, fp exception trapping)
> 3} The nan business which is related to (2)
> 4) dirent
> 5) a home for other POSIXisms. First on the list is gettimeofday.
> 6) a home for other C99isms.
> 7) Mumits' mingw_fseek that covers some of the deficiencies of W9x fseek
>
> This lib would become a system lib, automatically put into search list by
> specs. Many of the functions are needed for more complete libstdc++
> support, so I would like them to be available by default.
>
> In headers, the extras could be guarded by
> #ifndef __NO_ISIOCEXT
> or
> #ifndef __NO_POSIXEXT
> or both
>
> but they would all live together in the same lib.
>
> This would be ready for and become implemented with pre-release of 3.1
>
I agree, go for it. Beyond that though, I still think we need to draft
an RFC white paper. I've been building several packages recently since
I released MSYS and things just go smooth. I'm now trying to build
perl. I've a hints/mingw32.sh already created with a mingw32 default
system selectable. Once I get it building I'll upload it as a
mingw-contrib release. Once perl is in place then I want to add
autoconf, automake and libtool (Chuck Wilson's devel version). With
this supporting dll building out of the configure script will be just a
matter of using libtool.
I see us creating a Win32 package that uses a Win32 style installation.
I'm already looking at INNO Setup to accomplish this. INNO Setup is
written in DELPHI and is Open Source. From what I've learned so far
it'll be a useful tool for creating a complete MSYS,GCC,runtime,w32api
combined installation. We could even add the "Visual MinGW IDE" if we
really wanted to. Once I get a .iss (INNO Setup Script) template setup
for MSYS I'll upload it to CVS so that we can expand on it together.
I would like to see MinGW become the best developer solution for
Win32/64 and not just a solution.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

>
> I agree, go for it. Beyond that though, I still think we need to draft
> an RFC white paper.
Yes.
>I've been building several packages recently since
> I released MSYS and things just go smooth. I'm now trying to build
> perl. I've a hints/mingw32.sh already created with a mingw32 default
> system selectable. Once I get it building I'll upload it as a
> mingw-contrib release. Once perl is in place then I want to add
> autoconf, automake and libtool (Chuck Wilson's devel version). With
> this supporting dll building out of the configure script will be just a
> matter of using libtool.
>
> I see us creating a Win32 package that uses a Win32 style installation.
> I'm already looking at INNO Setup to accomplish this. INNO Setup is
> written in DELPHI and is Open Source. From what I've learned so far
> it'll be a useful tool for creating a complete MSYS,GCC,runtime,w32api
> combined installation. We could even add the "Visual MinGW IDE" if we
> really wanted to. Once I get a .iss (INNO Setup Script) template setup
> for MSYS I'll upload it to CVS so that we can expand on it together.
>
Sounds like MinGW-Max (the minguin that devoured Cleveland).
> I would like to see MinGW become the best developer solution for
> Win32/64 and not just a solution.
>
Golly, when do we sleep?
Danny
> Earnie.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
http://movies.yahoo.com.au - Yahoo! Movies
- Vote for your nominees in our online Oscars pool.

On 2002.02.27 23:58 Earnie Boyd wrote:
> ...
>
> I see us creating a Win32 package that uses a Win32 style installation.
> I'm already looking at INNO Setup to accomplish this. INNO Setup is
> written in DELPHI and is Open Source. From what I've learned so far
> it'll be a useful tool for creating a complete MSYS,GCC,runtime,w32api
> combined installation. We could even add the "Visual MinGW IDE" if we
> really wanted to. Once I get a .iss (INNO Setup Script) template setup
> for MSYS I'll upload it to CVS so that we can expand on it together.
>
> I would like to see MinGW become the best developer solution for
> Win32/64 and not just a solution.
>
> Earnie.
>
This is a very nice vision! I don't say "dream" because I believe it's
perfectly within our range!
José Fonseca
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com