From: topcoder@mindspring.com (Derek Greene) Subject: Re: directx 1 Aug 1997 17:45:19 -0700 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <3.0.3.32.19970801045705.0069f524.cygnus.gnu-win32@mail.mindspring.com> References: <3.0.3.32.19970731094435.00697934@mail.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: topcoder@mail.mindspring.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Original-To: Eric Britten In-Reply-To: <33E23580.F0D012D6@uci.edu> Original-Sender: owner-gnu-win32@cygnus.com thanks for the replies guys, but, i already knew about that URL, but he hasnt done enuf for me to worry with his stuff At 12:14 PM 8/1/97 -0700, you wrote: >Derek Greene wrote: > >Check out.... > http://dragon.acadiau.ca/~025668b/develop/cygnus/ > >I have also used gnuwin32 to use OLE & COM objects. I think directx >uses a similar interface. It's not easy, you must use C not C++ for >now. C++ cleans up your code alot, but it doesn't compile the Microsoft >headers at all. For some reason the g++ is more peticular about the >location of * in a function prototype that returns a pointer. > >The directx sample doesn't have any problems since it uses C. > >For instance, >int * __stdcall foo(); > >gives an error. but > >int __stdcall * foo(); > >does not. > >Another thing is that if you declare the calling convention for a member >function of a class, the calling convention is ignored. This may pose a >problem since OLE expects stdcall for member functions of COM objects. > >Hope this helps. > >Eric Britten > >> has ANYONE managed to port directx to gnu-win32? puh-leez say yes, >> puh-leez >> say yes....:) >> - >> For help on using this list (especially unsubscribing), send a message >> to >> "gnu-win32-request@cygnus.com" with one line of text: "help". > > > > - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".