The sources are available from http://www.redland.opensource.ac.uk/dist/source/ (master site) and also from the SourceForge site.
Note that using this rather than the bundles may require having some extra development tools. Presently this includes the gperf tool.
# sh, bash, ... CVSROOT=:pserver:anonymous@cvs.ilrt.org:/cvsroot export CVSROOT # csh, tcsh, ... setenv CVSROOT :pserver:anonymous@cvs.ilrt.org:/cvsroot cvs login Logging in to :pserver:anonymous@cvs.ilrt.org:2401/cvsroot CVS password: [return] cvs checkout redland/raptor cd redland/raptor
At this stage, or after a cvs update you will need to create the automake and autoconf derived files, as described below in create the configure program by using the autogen.sh script.
Raptor uses the GNU automake and autoconf to handle system dependency checking. It is developed and built on x86 Linux (Redhat 7.2 and Debian unstable) but is also used extensively locally on various versions of sparc Sun Solaris 2.x and tested as part of Redland on many other systems via the SourceForge compile farm.
If there is no configure program, you can create it using the autogen.sh script, as long as you have the automake and autoconf tools. Alternatively you can run them by hand with:
aclocal; autoheader; automake --add-missing; autoconf
(Ignore any warnings from autoconf about AC_TRY_RUN, it is caused by an autoconf macro and IMHO is an autoconf bug.)
The automake and autoconf tools have many different versions and at present they are being developed with automake 1.4-p5, autoconf 2.13 and libtool 1.4.2a (with debian patches for OSX support). It is expected that development will move to automake 1.6+, autoconf 2.53 and libtool 1.4.3 or newer.
Raptor also supports the following extra configure options:
Pick an XML parser to use - either libxml (default) or expat. If this option is not given, either will be used, with libxml preferred if both are present. These can either be installed system libraries or source trees in subdirectories of these sources named libxml, expat.
Raptor has been tested with various combinations of these libraries including expat 1.95.1 (on RedHat 7.2), expat 1.95.2-2 (on RedHat 7.3), expat 1.95.2-6 (on Debian 3.0), libxml 2.3.5 (on Debian unstable), libxml 2.4.10 (on RedHat 7.2), libxml 2.4.13 (on OSX 10.1.5), libxml 2.4.17 (on FreeBSD 4.5-RELEASE-p2), libxml 2.4.19 (on RedHat 7.2), libxml 2.4.23 (on Debian 3.0), libxml 2.4.24 (on FreeBSD 4.7-STABLE), libxml 2.4.25, 2.4.28, 2.4.30 (Debian unstable)
(Some libxml1 versions may work however this is not guaranteed or tested and libxml1 support may be removed from future releases.)
If everything is in the default place, do:
./configure
The most common configuration you will be doing something like this:
./configure --with-xml-parser=expat
Compile the parser and the test program rapper with;
make
Note: GNU make is probably required so it may be gmake or gnumake on your system
This test program can then be used with local RDF/XML content files like this:
rapper file:dc.rdf
It can also extract RDF content inside general XML when the --scan option is set. e.g. if some RDF/XML is embedded inside some XHTML, it could be extracted with:
rapper -s file:/path/to/test/doc.xhtml
You can also run it on N-Triples files like this:
rapper -n file:test.nt
The default output is a simple statement dump format, but it can
be changed to emit N-Triples by using the -o
option, like this:
rapper -o ntriples file:dc.rdf
You can build and run the built-in test suite with:
make check
which should emit lots of exciting test messages to the screen but
conclude with something like:
All n tests passed
if everything works correctly.
Copyright 2001-2002 Dave Beckett, Institute for Learning and Research Technology, University of Bristol