To install H/Direct-0.12 on Linux, two things had to be changed:

   * Move an #include to a more probable place (just guessing...):

-----------------------------------------------------------------------
diff -r -c hdirect-0.12.orig/lib/PointerSrc.c hdirect-0.12/lib/PointerSrc.c
*** hdirect-0.12.orig/lib/PointerSrc.c  Sat Oct 24 12:41:24 1998
--- hdirect-0.12/lib/PointerSrc.c       Tue Oct 27 16:02:44 1998
***************
*** 32,43 ****
  
  #if defined(_WIN32) && !defined(__CYGWIN32__) && defined(COM)
  #include <windows.h>
  #else
   #ifdef __CYGWIN32__
    #include <windows.h>
   #endif
  #include <stdlib.h>
- #include "comPrim.h"
  #endif
  
  #if defined(USESTACK) && (!defined(_WIN32) || defined(__CYGWIN32__))
--- 32,43 ----
  
  #if defined(_WIN32) && !defined(__CYGWIN32__) && defined(COM)
  #include <windows.h>
+ #include "comPrim.h"
  #else
   #ifdef __CYGWIN32__
    #include <windows.h>
   #endif
  #include <stdlib.h>
  #endif
  
  #if defined(USESTACK) && (!defined(_WIN32) || defined(__CYGWIN32__))
-----------------------------------------------------------------------

   * The library has to be built by a "make libhdirect.a" in
     hdirect-0.12/lib and not by a "make lib" in hdirect-0.12.

Hmmm, why on earth do the above things lead me to the sinister conclusion
that the main platform for testing H/Direct is not *nix anymore...?   :-)

Some remarks regarding the examples:

   * [pure]int rand(void); ???
     I really hope that rand is *not* a pure function...  :-}

   * int strncmp([in,string]char* s1,[in,string]char* s2,[in]int n);
     Shouldn't this read:
     int strncmp([in]FastString s1,[in]FastString s2,[in]int n);

In fear of "getChar :: HRESULT Char",
   Sven

-- 
Sven Panne                                        Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik                     FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen              Oettingenstr. 67
mailto:[EMAIL PROTECTED]            D-80538 Muenchen
http://www.pms.informatik.uni-muenchen.de/mitarbeiter/panne

Reply via email to