The advantage of a native port would be that cygwin comes with libtiff, libjpeg and libpng. Anyway, my problem was that MinGW defines __WIN32__, whereas cygwin defines _CYGWIN32__. So I had no framedriver in ftable.c :-( I am not sure if this fixes all issues, because I also changed vd_win32.c to not create the thread calling GRXMain, but rather create a thread that creates the graphics window and dispatches the messages. This was easy enough to do by creating grx.dll instead of libgrx.a and do the initialization in DllMain(). Thinking about this, I see no point why this cannot be moved to frame buffer creation stage... Hmm, I'll have a look into that.
Ciao Tom
PS: Sorry for responding a bit late, I was not subscribed to the mailing list.
From: Mariano Alvarez Fernandez Subject: GRX2.4.5 and MinGW/Cygwin Date: 15 Jan 2003, 22:50:51 Demmer, Thomas wrote:
Hi all, I have managed to compile GRX under Cygwin with gcc -mno-cygwin (this is essentially just using MinGW and MinGW-Runtime). gcc is version 3.2, just for the record. After some minor changes, it also compiles and links without warnings as a native cygwin application. It just doesn't run and hangs somewhere in GrSetMode(). Can anybody enlighten me what is missing to complete the port to native Cygwin?
Sorry, I don't know how to use Cygwin. But, what advantages would have a native cygwin port?
Thomas Demmer Kraft Foods R&D Munich Phone: +49 89 62738-6302 Fax: +49 89 62738-86302
Thought of the Day: Conscience is the inner voice that warns us somebody is looking -- H. L. Mencken