Re: [Mingw-users] Some MinGW basics

[John E. <jo...@ti...>]

Thanks Chris.  That's a long list of questions so just FYI....

> * How do you deal with the lack of fork(), symlink() and readlink() when 
> compiling with MSVC? The same should apply to MinGW.
> 
For symlink() and readlink() I've provided my own approximations.  For fork()/exec() I've substituted spawn().  It seems like spawn() would be the correct way to go for MinGW too, although I now suspect that the app wouldn't build under MinGW for other reasons, namely....


> * Does it have a Makefile?
> 

No.  The original build system was scons.


> * Does it use MFC or ATL? (neither are supported using MinGW as far as I 
> know)
> 
That's quite interesting...  The app I'm talking about is Ardour and I do know that others have tried building it with MinGW (unsuccessfully, from what I can gather).  It does use ATL quite extensively, so maybe that was the problem.


> * Does your app compile and run with the original MSVCRT C library?
> 
No.  I'm using MSVC 8.0.  Just out of interest, why is MinGW sticking with the old CRT from MSVC 6.0?  Is it just tradition?  Contrary to popular belief, newer versions of MSVC are much more standards compliant (in certain areas, anyway - one of which is ATL).  There's still very little C99 support of course but CRT 8.0 and later are light years ahead of version 6.0.  Is that the kind of move that would benefit MinGW?  Or even be practical??

John