X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=README;h=f06e7f5077fbfb179db61160d34e3c5fa113b205;hb=7bba4af5d54cef6c873309daf57b917868fc13e2;hp=94d81a0ec19abcbb0b9f4e282437b14141bb869f;hpb=d22fb3d5210a72c35afce35ee9779e7ccfa5da00;p=org.ibex.core.git

diff --git a/README b/README
index 94d81a0..f06e7f5 100644
--- a/README
+++ b/README
@@ -12,37 +12,30 @@ presented below:
       Start here. Includes a map of all other documentation and a
       description of the directory strucure
 
-- The XWT home page [www/ or http://www.xwt.org/]
+- The XWT home page [http://www.xwt.org/]
 
-      A complete copy of all static and dynamic content for
-      www.xwt.org is in the xwt/www/ directory.
-
-- The XWT tutorial [www/html/tutorial.html_]:
+- The XWT tutorial [http://www.xwt.org/tutorial.html]
 
       Gentle introduction to what XWT is, and how to write
       .xwt's. Good for anybody who wants to write XWT applications.
 
-- The XWT reference [www/html/reference.html]
+- The XWT reference [http://www.xwt.org/reference.html]
 
       Precise, technical spec of exactly how XWT works. Assumes
       familiarity with XWT (ie, you've read the tutorial). This is the
       authoritative source for how an XWT engine should
       behave.
 
-- Javadoc [www/html/javadoc/package-summary.html]
+- Javadoc [http://www.xwt.org/javadoc/]
 
-      The org.xwt.* packages are all documented with javadoc. If
-      you've just checked out or downloaded a fresh copy of the XWT
-      distribution, you can generate the javadoc by typing
-      "./ant www" at the root directory of the distribution. You
+      The org.xwt.* packages are all documented with javadoc. You
       should start by reading the package summary for org.xwt.Main,
       and work your way around from there.
 
-- Javasrc [www/html/javasrc/index.html]
+- Javasrc [http://www.xwt.org/javasrc]
 
       Javasrc generates a syntax-colored and hyperlinked html copy of
-      the XWT source code. To generate this documentation, type "./ant www"
-      from the root directory of the distribution.
+      the XWT source code.
 
 
 ______________________________________________________________________________
@@ -55,14 +48,6 @@ Directory Structure
    ant                   - a unix shell script to launch ant
    bin/                  - all binary stuff generated by ant builds
    build.xml             - ANT build file
-   doc/                  - documentation
-
-   www/                  - a copy of all static and dynamic content on xwt.org
-       etc/              - configuration files
-       html/             - static content -- files ending with an underscore get
-                           prefix.html/suffix.html/tagline.html added to them
-       launch/           - code for launch.xwt.org
-       src/              - source code for servlets running on xwt.org
 
    lib/                  - any third-party binary stuff needed during the build process
        javago            - a copy of the javago post-compilation bytecode inliner
@@ -117,17 +102,11 @@ list as of 20-Mar-2002:
 Valid <target>s are:
 
     build         - builds a binary for the selected platform
-    dist          - creates deployment materials for the selected platform in dist/
-    run           - runs the binary for the selected platform
 
 The following targets do not require that you specify a platform:
 
     compile       - compiles all .java's to .class'es
     clean         - empties bin/ and compiled binaries in dist/
-    www           - rebuild www/html/
-    push          - push changes to the web server via ssh (RSA auth)
-
-
 
 
 ______________________________________________________________________________
@@ -153,10 +132,11 @@ Building
   without it, however, since it puts additional strain on the gcc cvs
   server.
 
-  There are also two patches at the end of this file which can be
-  applied to the branch -- the first disables Win32 file locking (so
-  you can view XWT's log files while it is running), and the second
-  makes Throwable.printStackTrace() work.
+  There are also three patches at the end of this file which can be
+  applied to the branch -- the first fixes a bug related to
+  GetFullPathName, the second disables Win32 file locking (so you can
+  view XWT's log files while it is running), and the third makes
+  Throwable.printStackTrace() work.
 
   # create an install area
   export CLASSPATH=
@@ -203,7 +183,39 @@ Building
   make
   sudo make install
 
+- The Linux native version is still experimental. You should configure
+  your compiler with:
 
+  ../gcc/configure \
+                   --prefix=$PREFIX \
+                   --enable-languages=c,c++,java \
+                   --disable-nls \
+                   --enable-libgcj \
+                   --enable-threads=posix \
+                   --enable-hash-synchronization \
+                   --enable-static \
+                   --disable-interpreter
+
+
+______________________________________________________________________________
+GetFullPathName patch
+
+Index: natFileWin32.cc
+===================================================================
+RCS file: /cvs/gcc/gcc/libjava/java/io/natFileWin32.cc,v
+retrieving revision 1.9.2.1
+diff -u -r1.9.2.1 natFileWin32.cc
+--- natFileWin32.cc 16 Apr 2002 15:35:20 -0000  1.9.2.1
++++ natFileWin32.cc 14 May 2002 01:57:39 -0000
+@@ -106,7 +106,7 @@
+   LPTSTR unused;
+   char buf2[MAX_PATH];
+   if(!GetFullPathName(buf, MAX_PATH, buf2, &unused))
+-    throw new IOException (JvNewStringLatin1 ("GetFullPathName failed"));
++    return NULL;
+ 
+   // FIXME: what encoding to assume for file names?  This affects many
+   // calls.
 
 
 ______________________________________________________________________________