[Adonthell-commits] CVS: adonthell INSTALL,1.26,1.27 README.BeOS,1.6,1.7 configure.in,1.78,1.79

[Kai Sterker <address@hidden>]

Update of /cvsroot/adonthell/adonthell
In directory subversions:/tmp/cvs-serv23409

Modified Files:
        INSTALL README.BeOS configure.in 
Log Message:
CHANGED: Keep everything in one directory under BeOS (just like Win32)
FIXED some errors in the documentation


Index: INSTALL
===================================================================
RCS file: /cvsroot/adonthell/adonthell/INSTALL,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -r1.26 -r1.27
*** INSTALL     19 Sep 2002 14:00:55 -0000      1.26
--- INSTALL     15 Dec 2002 17:23:29 -0000      1.27
***************
*** 136,141 ****
--- 136,145 ----
  information in this file. Use 'mtrace adonthell $MALLOC_TRACE'
  to finally display any occurrence of memory leaks.
+   
    A much more convenient way to check for memory leaks is the
  'memprof' tool: http://people.redhat.com/~otaylor/memprof
+   
+   Even better than memprof, but not as easy to use is valgrind:
+ http://developer.kde.org/~sewardj/
  
  

Index: README.BeOS
===================================================================
RCS file: /cvsroot/adonthell/adonthell/README.BeOS,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** README.BeOS 4 Dec 2002 17:09:47 -0000       1.6
--- README.BeOS 15 Dec 2002 17:23:30 -0000      1.7
***************
*** 30,34 ****
  
  This will add the /boot/develop/tools/gnupro/lib directory to the 
! systems library path (after a reboot). That is useful, as all the
  libraries we install go into that directory. 
  
--- 30,34 ----
  
  This will add the /boot/develop/tools/gnupro/lib directory to the 
! system library path (after a reboot). That is useful, as all the
  libraries we install go into that directory. 
  
***************
*** 69,76 ****
  The various editors that come with Adonthell are not really written
  with portability in mind. Some of them might compile, others might
! not. Espacially those depending on GTK+ might cause trouble. However,
  for playing Adonthell, you won't need them, so it's no big loss.
  
  
  Contact:
  ========
--- 69,84 ----
  The various editors that come with Adonthell are not really written
  with portability in mind. Some of them might compile, others might
! not. Especially those depending on GTK+ might cause trouble. However,
  for playing Adonthell, you won't need them, so it's no big loss.
  
  
+ Known issues:
+ =============
+ 
+ If you want to run Adonthell in fullscreen mode, you'll have to switch
+ manually to 640x480 before starting the game. This is a problem with
+ SDL though. 
+ 
+ 
  Contact:
  ========
***************
*** 80,81 ****
--- 88,95 ----
  here or want to contribute a patch please drop me a few lines.
  
+ 
+ Credits:
+ ========
+ 
+ Many thanks to Shard, who did a wonderful debugging job. Without his
+ help, you wouldn't be able to play Adonthell on the BeOS.

Index: configure.in
===================================================================
RCS file: /cvsroot/adonthell/adonthell/configure.in,v
retrieving revision 1.78
retrieving revision 1.79
diff -C2 -r1.78 -r1.79
*** configure.in        4 Dec 2002 17:09:47 -0000       1.78
--- configure.in        15 Dec 2002 17:23:30 -0000      1.79
***************
*** 76,81 ****
      ;;
      *-*-beos*)
!       gamedatadir="/boot/home/share/adonthell"
!       DEFS="$DEFS -DDATA_DIR=\"\\\"$gamedatadir\\\"\""
      ;;
      *)
--- 76,80 ----
      ;;
      *-*-beos*)
!       gamedatadir=""
      ;;
      *)
***************
*** 451,454 ****
--- 450,456 ----
    *-*-cygwin* | *-*-mingw32*)
      echo "Building for Windows target."
+   ;;
+   *-*-beos*)
+     echo "Building for BeOS target."
    ;;
    *)