Winelib and <io.h>

[Hans Christian Studt]

Using (pached) winemaker I still have problems with <io.h>

sed -e 's,@bindir@,/usr/local/bin,g' -e 's,@winelibdir@,.,g' 
./wineapploader.in >wineapploader || rm -f wineapploader
make[1]: Entering directory 
`/user/home/hcs/Wine/winelib/compile/bb4win/blackbox'
LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/local/bin/wrc -J -m 
  -I.  -I/usr/local/include/wine/windows -o Blackbox.res 
Blackbox.rc
/usr/local/bin/wineg++ -c  -I. 
-I/usr/local/include/wine/windows -g -O2 -fpermissive 
-fno-for-scope    -D_REENTRANT -o BBApi.o BBApi.cpp
In file included from BBApi.cpp:34:
Menu/MenuMaker.h:53:16: io.h: Ingen sådan fil eller filkatalog

There was a discussion on a subject related to io.h started on 
this list 9. january 2003.
What exactly were the outcome ???
Is there a resolution or a workaround ???

I can still try out Ming/Cygwin but how would that change the 
<io.h> problem ???

[Dimitrie O. Paun]

On Fri, 31 Jan 2003, Hans Christian Studt wrote:
> I can still try out Ming/Cygwin but how would that change the 
> <io.h> problem ???

It will not, but it will make it much more easy for us to fix.
Basically, if it works under MinGW, it should work under Wine.
Thing is, you don't want to have to fix _all_ the porting
problems at once. MinGW provides an _ideal_ midstep in the
process, and it comes almost for free, because it doesn't
imply a detour to take it. Essentially you have to pass through
the point where the app builds under MinGW, you might as well
try and see that it does. This removes a _lot_ of the uncertainties
in later stages, making them so much easier to debug and fix.

That being said, try to compile using the MSVCRT headers. To
do that, just pass -mno-cygwin to winegcc, see if that works.