X-Git-Url: http://git.kpe.io/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fintro.xml;h=a717241b043dd73ce0dddeb80a158595961dc49c;hb=b1fe1b3516bd2534766f31083660ea0f24021376;hp=57666effbc57eb68eac54356f0f6796a8cb0bf0e;hpb=967266c94b00f91e5967b8330fe2b9134b0c0447;p=clsql.git
diff --git a/doc/intro.xml b/doc/intro.xml
index 57666ef..a717241 100644
--- a/doc/intro.xml
+++ b/doc/intro.xml
@@ -106,12 +106,18 @@
implementations of &uffi;. The following implementations are supported:
- &acl; v6.2 on Debian Linux, FreeBSD 4.5, and Microsoft Windows XP.
- &lw; v4.3 on Debian Linux and Microsoft Windows XP.
- &cmucl; 18e on Debian Linux, FreeBSD 4.5, and Solaris 2.8.
- &sbcl; 0.8.5 on Debian Linux.
+ &acl; v6.2 and 7.0b on Debian Linux x86 &
+ x86_64 & PowerPC, FreeBSD 4.5, and Microsoft Windows
+ XP.
+ &lw; v4.3 on Debian Linux and Microsoft
+ Windows XP.
+ &cmucl; 18e on Debian Linux, FreeBSD 4.5, and
+ Solaris 2.8.
+ &sbcl; 0.8.5 on Debian
+ Linux.
&scl; 1.1.1 on Debian Linux.
- &openmcl; 0.14 on Debian Linux PowerPC.
+ &openmcl; 0.14 on Debian Linux
+ PowerPC.
@@ -126,6 +132,7 @@
socket connections.
&sqlite;.
Direct &odbc; interface.
+ &oracle;
Allegro's DB interface (&aodbc;).
@@ -184,7 +191,7 @@
- Load &uffi;
+ Add &uffi; path
Unzip or untar the &uffi; distribution which creates a directory
for the &uffi; files. Add that directory to &asdf;'s asdf:*central-registry*.
@@ -194,12 +201,11 @@
directory.
(push #P"/usr/share/lisp/uffi/" asdf:*central-registry*)
-(asdf:operate 'asdf:load-op :uffi)
- Load &md5; module
+ Add &md5; path
If you plan to use the clsql-postgresql-socket interface, you
must load the md5 module. Unzip or untar the cl-md5
@@ -211,13 +217,12 @@
/usr/share/lisp/cl-md5/ directory.
(push #P"/usr/share/lisp/cl-md5/" asdf:*central-registry*)
-(asdf:operate 'asdf:load-op :md5)
- Load &clsql; modules
+ Add &clsql; path and load module
Unzip or untar the &clsql; distribution which creates a
directory for the &clsql; files. Add that directory to &asdf;'s
@@ -225,34 +230,28 @@
pushing the pathname of the directory onto this variable. The
following example code assumes the &clsql; files reside in the
/usr/share/lisp/clsql/ directory. You need
- to load, at a minimum, the main clsql system
- and at least one interface system. The below example show loading
- all &clsql; systems.
+ to load the clsql system.
(push #P"/usr/share/lisp/clsql/" asdf:*central-registry*)
-(asdf:operate 'asdf:load-op 'clsql-base) ; base CLSQL package
-(asdf:operate 'asdf:load-op 'clsql-mysql) ; MySQL interface
-(asdf:operate 'asdf:load-op 'clsql-postgresql) ; PostgreSQL interface
-(asdf:operate 'asdf:load-op 'clsql-postgresql-socket) ; Socket PGSQL interface
-(asdf:operate 'asdf:load-op 'clsql-odbc) ; ODBC interface
-(asdf:operate 'asdf:load-op 'clsql-sqlite) ; SQLite interface
-(asdf:operate 'asdf:load-op 'clsql-aodbc) ; Allegro ODBC interface
(asdf:operate 'asdf:load-op 'clsql) ; main CLSQL package
- Run test suite
+ Run test suite (optional)
- After loading &clsql;, you can execute the test suite. A
- configuration file named
+ The test suite can be executed using the &asdf;
+ test-op operator. If &clsql; has not been
+ loaded with asdf:load-op, the
+ asdf:test-op operator will automatically load
+ &clsql;. A configuration file named
.clsql-test.config must be created in
your home directory. There are instructures on the format of
- that file in the tests/tests.lisp file in
- the &clsql; source directory. After creating that file, you
- can run the test suite with &asdf;:
+ that file in the tests/README. After
+ creating .clsql-test.config, you can run
+ the test suite with &asdf;:
(asdf:operate 'asdf:test-op 'clsql)