projects
/
yaz-moved-to-github.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
8df7d26
)
Mention xsltproc. Refer to SRU rather than SRW
author
Adam Dickmeiss
<adam@indexdata.dk>
Fri, 13 Oct 2006 11:25:24 +0000
(11:25 +0000)
committer
Adam Dickmeiss
<adam@indexdata.dk>
Fri, 13 Oct 2006 11:25:24 +0000
(11:25 +0000)
README
patch
|
blob
|
history
diff --git
a/README
b/README
index
6807a65
..
fbdd32c
100644
(file)
--- a/
README
+++ b/
README
@@
-1,11
+1,11
@@
-YAZ toolkit - $Id: README,v 1.48 2006-02-01 20:07:20 adam Exp $
+YAZ toolkit - $Id: README,v 1.49 2006-10-13 11:25:24 adam Exp $
Copyright (C) 1995-2006, Index Data ApS.
See the file LICENSE for details.
The primary output of the source here is the YAZ library, which
contains support functions for implementing the server or client
Copyright (C) 1995-2006, Index Data ApS.
See the file LICENSE for details.
The primary output of the source here is the YAZ library, which
contains support functions for implementing the server or client
-role of Z39.50 and SRW.
+role of Z39.50 and SRU.
On Unix, GNU configure is used to configure YAZ and generate Makefiles.
Type "./configure", then "make" to build YAZ. Read
On Unix, GNU configure is used to configure YAZ and generate Makefiles.
Type "./configure", then "make" to build YAZ. Read
@@
-17,7
+17,7
@@
On Windows, a MS Visual Studio makefile is provided (nmake). The commands
should do. Refer to doc/installation.win32.html for details.
Note: If you are using the CVS snapshot of YAZ you must have autoconf,
should do. Refer to doc/installation.win32.html for details.
Note: If you are using the CVS snapshot of YAZ you must have autoconf,
-automake and libtool installed. Before running configure, create
+automake, libtool and xsltproc installed. Before running configure, create
support files by running buildconf.sh in the top-level directory of YAZ.
In any case refer to the documentation in sub directory doc or read
support files by running buildconf.sh in the top-level directory of YAZ.
In any case refer to the documentation in sub directory doc or read