On Mon, 9 Jun 1997 12:09:21 +0100 (WET DST) Jan-Jaap van der Heijden janjaap@Wit381304.student.utwente.nl wrote:

I have converted just enough headers to be able to compile a basic GUI application, where you do all the message handling yourself (no object windows available :-(

No sweat about object Windows (something can be done about that later). Can you please send me a copy of your converted headers? Thanks. There is no point in duplicating efforts, and I don't want to reinvent the wheel.

I did this for cygwin32 b16. Then I focussed more on the unix ascpects for some time, but now I have a b18 GPC compiler, and I'm working on some cygwin32 things (DLL's, building the RTS as a DLL etc.) I'm not sure that function attibutes survive through the GPI mechanism (they didn't for b16) so using units may not be possible.

Well, I could simply "$INCLUDE" the sources - which is what I did when I first started using GPC anyway.

You need the "__attribute__((stdcall))" feature to access win32 API functions.

Yes, I saw this in some of the sample programs.

Building DLL's on doze95 is difficult (not just for GPC) in b18. NT seemed fine, but my NT machine crashed a HD this weekend :-(

Ooops!

...

PS: I have found that many things are different under CygWin from the rest (e.g., the "stat" structure; the "errno", which is implemented as a macro); and many things which are in standard C headers are missing (e.g., strlwr(), strupr(), stricmp, etc.).

cygwin32 is basically BSD. I don't know about the unix (?) that cygwin32 differs from in your opinion,

I was actually comparing it to the emx and djgpp headers - which I suppose I shouldn't. I didn't know that cygwin32 was based on BSD.

Best regards, The Chief Dr Abimbola A. Olowofoyeku (The African Chief, and the Great Elephant) Author of: Chief's Installer Pro v3.60 for Win16 and Win32. Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ E-mail: laa12@cc.keele.ac.uk