X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=README;h=fed29f0c77925feaff19b114d245df7f6f9eac97;hb=f9a418c3893f421d2f34ca4577691724a62e2f9f;hp=bbe83b7a7ecfaee9ba06aa332250d6015a697dcf;hpb=80c104c764dcb0bc4a4eb1a3e7fac22e65623db3;p=org.ibex.core.git diff --git a/README b/README index bbe83b7..fed29f0 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 @@ -100,10 +85,16 @@ Directory Structure ______________________________________________________________________________ Build Targets -To build, make sure your $JAVA_HOME points to jdk1.2 or later, and type + *** XWT now requires JDK 1.4 or later to build *** + +To build, make sure your $JAVA_HOME points to jdk1.4 or later, and type ./ant -Dplat= +If you're using jdk1.2 or jdk1.3 to compile, you should remove +src/org/xwt/plat/Java14.java, since it can only be compiled with +jdk1.4+. + The name of any class in org.xwt.plat is a valid ; here is a list as of 20-Mar-2002: @@ -113,17 +104,11 @@ list as of 20-Mar-2002: Valid 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) - - ______________________________________________________________________________ @@ -149,10 +134,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= @@ -199,29 +185,18 @@ Building make sudo make install +- The Linux native version is still experimental. You should configure + your compiler with: - - -______________________________________________________________________________ -File Locking Patch - -Index: java/io/natFileDescriptorWin32.cc -=================================================================== -RCS file: /cvs/gcc/gcc/libjava/java/io/natFileDescriptorWin32.cc,v -retrieving revision 1.5.2.2 -diff -u -r1.5.2.2 natFileDescriptorWin32.cc ---- java/io/natFileDescriptorWin32.cc 10 Mar 2002 03:34:59 -0000 1.5.2.2 -+++ java/io/natFileDescriptorWin32.cc 27 Apr 2002 08:40:40 -0000 -@@ -112,7 +112,7 @@ - create = CREATE_ALWAYS; - } - -- handle = CreateFile(buf, access, share, NULL, create, 0, NULL); -+ handle = CreateFile(buf, access, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, create, 0, NULL); - - if (handle == INVALID_HANDLE_VALUE) - { - + ../gcc/configure \ + --prefix=$PREFIX \ + --enable-languages=c,c++,java \ + --disable-nls \ + --enable-libgcj \ + --enable-threads=posix \ + --enable-hash-synchronization \ + --enable-static \ + --disable-interpreter ______________________________________________________________________________