Table of Contents

• Using Stable Binaries
  • Prebuilt Virtuoso binaries
  • Using Docker Hub
  • Using Maven Central
• Building VOS from Source
  • Package Dependencies
    • Core Dependencies
    • Recommended Packages
    • Specific Usage Cases
    • Linux
    • macOS
  • Building
  • Diskspace Requirements
• Starting Virtuoso

For convenience, you can download prebuilt binaries for most Linux, macOS and Windows platforms from the latest stable release on Github.

Previous releases are also backed-up on Sourceforge.

For more information about using the the Virtuoso Docker image, visit Docker Hub.

Virtuoso JDBC drivers, as well as Jena, Sesame and RDF4j providers, can be downloaded from Maven Central.

Windows requires special instructions. Please see README.Windows.md for details.

First, checkout a clone of the git repository:

$ git clone https://github.com/openlink/virtuoso-opensource.git
$ cd virtuoso-opensource

The default and recommended branch is develop/7. Users requiring a slower update cycle may prefer stable/7 instead.

For a minimal build with core VOS functionality, ensure you have the following packages and recommended versions installed:

The Minimum and Upto columns specify known-good versions for each package. Other versions, both older and newer, might work, but are untested and could cause problems.

You can test the installed version of each package by running it with --version except openssl, where the command is openssl version.

In addition to the above core, we recommend the following:

• libedit makes the isql commandline utility more usable.
• bzip2 and xz are useful for bulk-loading large amounts of RDF data.

The following packages are required if you have specific use-cases in mind:

Virtuoso has support for GeoSPARQL functions which requires the proj4, geos and shapefileio plugins. Building these is the subject of a separate document: README.GeoSPARQL.md.

Install the required dependencies - pick one of the following lines for your OS / distribution and then resume at the "Building" section below:

$ sudo apt install build-essential autoconf automake libtool flex bison gperf gawk m4 make libssl-dev

$ sudo apt install libreadline-dev libbz2-dev liblzma-dev

$ sudo yum install autoconf automake gcc libtool flex bison gperf gawk m4 make openssl openssl-devel

$ sudo yum install bzip2-devel xz-devel libedit-devel

$ sudo yum --enablerepo=rhui-REGION-rhel-server-optional install gperf

$ sudo yum --enablerepo=PowerTools install gperf

$ sudo yum install autoconf automake gcc libtool flex bison gperf gawk m4 make openssl openssl-develop

$ sudo zypper install autoconf automake gcc libtool flex bison gperf gawk m4 make openssl libopenssl-3-devel

$ sudo zypper install libedit-devel libbz2-devel xz-devel

brew install autoconf automake gcc libtool flex bison gperf gawk m4 make [email protected]

To (re)generate the configure script and all related build files, use the supplied script in your working directory:

$ ./autogen.sh

Assuming this runs successfully,

$ ./configure --enable-maintainer-mode --prefix=/opt/virtuoso-opensource --with-layout=openlink

• on macOS, add a pointer to find OpenSSL from homebrew:

$ ./configure --enable-maintainer-mode --prefix=/opt/virtuoso-opensource --with-layout=openlink --enable-openssl=/opt/homebrew/Cellar/[email protected]/3.0.15/

and then

$ make -j4

To run the test suite (optional):

$ make check

and finally

$ sudo make install

VOS can be configured with many options and VAD packages, for example libshape, libgeos, libproj, ImageMagick and other hosting modules. Many of these will require further development versions of supporting libraries of their own.

For further information, run:

$ ./configure --help

Certain build targets are only enabled when running configure with the --enable-maintainer-mode flag.

The installer supports multiple different filesystem layouts through the --with-layout= option.

The build produces a demo database and Virtuoso application packages that are quite large. At least 1.2 GiB of free space should be available in the build file system.

When running `make install', the target file system should have about 300 MB free. By default, the install target directories are under /usr/local/.

Running the testsuite will require approximately 2 GiB extra diskspace.

The minimum working configuration consists of the server executable and config files plus database, no more than a few MB for the server executable, depending on platform and options.

Change into the installation's database/ subdirectory and start the server:

$ cd /opt/virtuoso-opensource/database

$ ls
virtuoso.ini

For the first run, to illustrate the potential console output, we run it in debug foreground mode:

$ ../bin/virtuoso-t -df

The server will take a few seconds to start, install the Conductor VAD and eventually say it's online:

...
15:14:08 INFO: PL LOG: Installation with dependencies complete
15:14:08 INFO: Checkpoint started
15:14:08 INFO: Checkpoint finished, log reused
15:14:08 INFO: HTTP/WebDAV server online at 8890
15:14:08 INFO: Server online at 1111 (pid 50403)

In normal use, the server can be run without any arguments

../bin/virtuoso-t

and it will detach from the console, leaving its output only in virtuoso.log.

At this point, you can open http://localhost:8890/ in your browser. This is the welcome home page with links to Conductor (http://localhost:8890/conductor) and the SPARQL endpoint (http://localhost:8890/sparql).

Additionally, from the terminal, you can also run

../bin/isql

for the SQL interface (port 1111 by default).