Project: JNA

Revision: 685

Author: twalljava

Date: 04 Sep 2008 11:34:24

• /trunk/www/index.html

  ......	@@ -3,7 +3,7 @@
  3	3	<meta name="author" content="Timothy Wall">
  4	4	<meta name="keywords" content="java,jna,jni,c,c++,native,method,function,call,ctypes,ffi,foreign function interface,jdirect,jinvoke,pinvoke,platform invoke,native library access,native access,call native from java,java c library,easy jni,call c from java,avoid jni,jni alternative,jni replacement,legacy,call from java">
  5	5	<meta name="description" content="Java Native Access (JNA): access native libraries with pure Java code.">
  6		<meta name="date" content="2008-08-14">
  	6	<meta name="date" content="2008-09-04">
  7	7	<title>Java Native Access (JNA): Pure Java access to native libraries</title>
  8	8	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  9	9	</head>
  ......	@@ -552,6 +552,7 @@
  552	552	<li>Tips and recommended usage of JNA: Likely danger areas, failure modes, best practices, multithreading, etc.</li>
  553	553	<li>Native library definitions for the more useful libraries on various platforms; for example, <code>user32</code> on Windows. This is important not for having an exhaustive library definition but to illustrate all the different ways a native library may need to be mapped.</li>
  554	554	<li>Testing on various JDK versions and platforms (linux flavors!).</li>
  	555	<li>See the TODO file in the project directory for more up-to-date items.</li>
  555	556	</ul>
  556	557	<p>
  557	558
  ......	@@ -560,7 +561,7 @@
  560	561	<h3>Building and Multi-platform support</h3>
  561	562	JNA has been built and tested on OSX (ppc, x86, x86_64), linux (x86, amd64),
  562	563	FreeBSD/OpenBSD (x86, amd64), Solaris (x86, amd64, sparc, sparcv9) and Windows
  563		(x86). The ant build script's test target will build and run the test suite,
  	564	(x86, amd64). The ant build script's test target will build and run the test suite,
  564	565	which has decent coverage and is a quick way to determine if your environment
  565	566	is set up correctly.<p>
  566	567	If you want to do a build yourself, you'll need <a