There are several ways to get the sources. The most stable and tested versions are the sources shipped with each release and these are recommended as the first place to start. If you want to get a newer set, then there are nightly snapshots made of the development sources, which may not yet be committed to Subversion. For the latest developent sources, anonymous Subversion access is available but this may require some configuring of developer tools that are not needed for the snapshot releases.
The source bundle and package files contain all the HTML files and documentation provided on the web site.
Every release comes with full sources and these are available from http://download.librdf.org/source/ master site as well as the SourceForge site.
NOTE: Redland switched to use Subversion for version control after the 1.0.3 release. If you were using CVS, you will need to re-check out the sources.
Each night a snapshot distribution is attempted using the current
development sources (that may not even be commited to subversion), using the
make dist target of the automake system. If this target
completes, these snapshots are then made available from:
http://download.librdf.org/snapshots/source/
(binary snapshot releases are also attempted each night from the
same sources).
svn checkout http://svn.librdf.org/repository/raptor/trunk/ raptor svn checkout http://svn.librdf.org/repository/rasqal/trunk/ rasqal svn checkout http://svn.librdf.org/repository/librdf/trunk/ librdf cd librdf ln -s ../raptor ln -s ../rasqal
At this stage, or after a svn 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.
Building Redland in this way requires some particular development
tools not needed when building from snapshot releases - automake,
autoconf, swig and those also required by Raptor and Rasqal if they are built
See the
Raptor install document
and
Rasqal install document
for the details of requirements.
The autogen.sh script looks for the newest versions
of the auto* tools and checks that they meet the minimum versions.
Redland uses the GNU automake and autoconf to handle system dependency checking. It is developed and built on x86 Linux but is also tested on multiple systems locally and via SourceForges' compile farm where it currently builds on Debian/RedHat Linux (x86, Alpha, PPC and Sparc), FreeBSD (x86), NetBSD (x86), OpenBSD (x86) and Apple OSX (PowerPC).
Configure tries very hard to find several programs and libraries that Redland might need. These include the storage modules (Berkeley/Sleepycat DB, MySQL, PostgreSQL 3store), the XML parsers -- via Raptor's configure -- and various others. A summary of the modular parts found is given at the end of the configure run. Several options to configure given below can be used to point to locations or names of dependencies that cannot be automatically determined.
configure programIf there is no configure program, you can create it
by running the autogen.sh script, as long as you have the
automake and
autoconf
tools. This is done by:
./autogen.sh
and you can also pass along arguments intended for configure (see below for what these are):
./autogen.sh --prefix=/usr/local/somewhere
On OSX you may have to explicitly set the
LIBTOOLIZEvariable for thelibtoolizeutility since on OSXlibtoolizeis a different program:LIBTOOLIZE=glibtoolize ./autogen.sh
Alternatively you can run the automake and autoconf programs by hand with:
aclocal; autoheader; automake --add-missing; autoconf
The automake and autoconf tools have many different versions and at present development is being done with automake 1.8.3 (minimum version 1.7), autoconf 2.59 (minimum version 2.54) and libtool 1.5.4 (minimum version 1.4). These are only needed when compiling from Subversion sources. autogen.sh enforces the requirements. In future development will move to require automake 1.8, autoconf 2.58 and libtool 1.5.
configureSee also the generic GNU installation instructions in
INSTALL for information about general options
such as --prefix etc.
--disable-assertDisable compiling run-time assertions. In maintainer mode, assertion failures are fatal.
--disable-assert-messagesDisable compiling run-time assertion failure messages. In maintainer mode, assertion failures are fatal after the assertion failure is reported.
--enable-digests=LISTSelect the list of content digests to be included if the are
availble. The valid list of digests are: md5 sha1
ripem160 (the default). The digest functions can be provided
by external libraries such as the
OpenSSL libcrypto library or by
provided portable versions (only MD5 supported in this
release).
--enable-parsers=LISTSelect the list of RDF parsers to be included if the are availble. The
valid list of RDF parsers is currently only raptor (the default)
since the older repat parser has been removed. Raptor uses either of
libxml2 (prefered) or expat. Redland requires the Raptor parser for
other functionality, so it cannot be disabled.
--with-bdb= ROOT or noEnable use of the Berkeley / Sleepycat DB library installed at
ROOT. That means ROOT/include must
contain the BDB header db.h and ROOT/lib
must contain the library libdb.a (or whatever shared library
version/name your system uses).
If the value is no, the BDB backend store is disabled.
Berkeley DB is known as Sleepycat DB (after version 2) and distributed and supported by SleepyCat Software. Versions 4.1.25, 4.1.24, 4.0.14, 3.3.11, 3.2.9, 3.1.17, 3.1.14, 2.7.7 and 2.4.14 have been tested and work. Some systems do not come installed with a working Berkeley/Sleepycat DB so on those systems, Redland will have no persistent storage unless BDB is built separately and enabled via this option.
Note: If you change installed versions of BDB then you will need to re-configure Redland carefully to let it discover the features of the newer BDB as follows:
rm -f config.cache make clean ./configure ... # any configure arguments here
(plus you might need to use the
dbX_upgrade
utility to update the BDB database files to the formats supported by
the newer version X - see the BDB documentation to find out
if this is required.)
If the BerkeleyDB is installed in different places from
ROOT/lib (library) and
ROOT/include (header) or
the library name is something that can't be worked out automatically,
then you can use the next set of options to specify them.
If all of the BDB options are omitted, Redland will do a best efforts guess to find the newest BDB installation but this may not work for all configurations.
--with-bdb-lib=LIBDIR--with-bdb-include=INCDIR--with-bdb-name=NAMEUse Berkeley DB with the installed library in LIBDIR
and the db.h header in INCDIR and
the installed library called NAME
like -lNAME. This is relative to LIBDIR.
All of these options can be omitted and configure will
try to find or guess the values from the system.
For example, to compile redland on OSX with fink might require a configure line something like this:
./configure --with-bdb-lib=/sw/lib \
--with-bdb-include=/sw/include/db3
The name of the BDB library was correctly discovered for this
configuration, as db-3.3.
If all of the BDB options are omitted, Redland will do a best efforts guess to find the newest BDB installation but this may not work for all configurations.
(At present, Redland knows of the default /sw Fink
installation directory and will look there for BDB installs)
Enable signing of memory allocations so that when memory is allocated with malloc() and released free(), a check is made that the memory was allocated in the same library.
--with-mysql(=CONFIG|yes|no)Enable use of the Redland MySQL 3.x, 4.x triple store backend
using CONFIG for the mysql_config program. The
default when either no argument is given, or
--with-mysql alone, is to search for
mysql_config on the search PATH. With
--with-mysql=no, this store is disabled.
Versions 3.23.58 and 4.0.4 have been tested and work.
--with-openssl-digestsEnable the content digests provided by the OpenSSL libcrypto library (MD5, SHA1 and RIPEMD160) if the library is available. configure will automatically enable this unless disabled by setting this option to no.
--with-postgresql(=CONFIG|yes|no)Enable use of the Redland PostgreSQL triple store backend
using CONFIG for the pg_config program. The
default when either no argument is given, or
--with-postgresql alone, is to search for
pg_config on the search PATH. With
--with-postgresql=no, this store is disabled.
--with-raptor= system or internal
This option tells redland to use either the system installed version
of raptor
or the internal version. If the option is omittted,
redland will guess and choose either the system one, if new enough or
the internal one (always present). If --with-raptor=system
is used and redland discovers that the system raptor is too old,
a warning will be given but the configuration will continue.
--with-rasqal= system or internal
This option tells redland to use either the system installed version
of rasqal
or the internal version. If the option is omittted,
redland will guess and choose either the system one, if new enough or
the internal one (always present). If --with-rasqal=system
is used and redland discovers that the system rasqal is too old,
a warning will be given but the configuration will continue.
--with-sqlite=(yes|no|2|3)Enable use of SQLite
triple store backend with a particular version V2 or V3,
an automatically chosen one with yes or disable it
(with no).
--with-threestore(=CONFIG|yes|no)Enable use of the AKT project
3store triple store
backend using CONFIG
for the 3store-config program. The default when either
no argument is given, or --with-threestore alone, is to search for
the 3store-config on the search PATH. With
--with-threestore=no, this store is disabled.
--with-xml-parser=NAMEPick an XML parser to use for Raptor - either libxml
(default) or expat. If this option is not given,
either will be used, with libxml preferred if both are present.
One of these much be available for Raptor to parse XML syntaxes.
Raptor has been tested with various combinations of these libraries that are described further in the Raptor install documentation.
WARNING If the Sleepycat/Berkeley DB library is installed
in a non-default directory, when the final linking occurs, the
libraries may not be found at run time. To fix this you will need to
use a system-specific method of passing this information to the
run-time loader. On most systems you can set the LD_LIBRARY_PATH
environment variable to include the directory where the libdb*
libraries are found. (On OSX this is DYLD_LIBRARY_PATH) You can also
configure it via a system wide file - see the ld,
ld.so orld.so.1 manual pages for
details.
If everything is in the default place, do:
./configure
More commonly you will be doing something like this, when giving the installation location of Berkeley/Sleeypcat DB:
./configure --with-bdb=/usr/local/berkeleydb
If you are having problems with configuring several times when adding or removing options, you may have to tidy up first with either of these:
make clean rm -f config.cache
make
You can build and run the built-in tests for Redland 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.
(If you have got all the required subsidiary development tools,
you can also do make distcheck which does a longer
check that the distribution installation, configuring and building
works. This does not perform any additional core testing).
To install the C library (static and shared typically) plus the interface header (.h) files do:
make install
Once the library has been configured and built, there are
several C example programs that can be used. They are
in the examples sub-directory and can be built with:
cd examples make
(This may be done by the initial 'make' automatically).
If no Berkeley DB was found by configure, some of the examples will fail since there is no on-disk storage system available. To change them to use the in-memory hashes, edit the lines reading something like
storage=librdf_new_storage("hashes",
"test",
"hash_type='bdb',dir='.'");
to read
storage=librdf_new_storage("hashes",
"test",
"hash_type='memory',dir='.'");
The rdfproc utility in the utils directory exercises
the majority of the useful parts of the Redland API and can
demonstrate many ways to store, search and manipulate the graph from C.
example1 uses a RDF parser, if you have one available, to
parse a URI of RDF/XML content, store it in multple Berkeley DB
hashes on the disk and run queries against them. It takes two
arguments, the first the URI of the RDF/XML content (or
file:filename) and the second, optional one, is the
name of the RDF parser to use.
example2 does not use a RDF parser, but reads from a
simple triple dump format and again stores the data on disk in
multiple Berkeley DB hashes.
example3 contains a 10 line main program that creates
an RDF model, a statement, adds it to the model and stores it on
disk.
example4 contains an example of how to
serialize an RDF model to a syntax.
Copyright (C) 2000-2008 Dave Beckett
Copyright (C) 2000-2005 University of Bristol