Building From Subversion

Contents

  1. Introduction
  2. Prerequisites
  3. Check Out the Repository
  4. Build & Install the Packages

1) Introduction

Building and installing from Subversion is perhaps the most difficult method of installing XmlPL. You may first want to consider the other options listed on the Download page. However, there are advantages. If want access to the most bleeding edge version of XmlPL this is the way to get it. Also, if you want to contribute to the project you should probably start here.

To build from the Subversion repository you must have a Subversion client installed on you system.

2) Prerequisites

In order to build XmlPL you will need to install the same prerequisites as are required for the XmlPL builder install method. See Install for more information.

3) Check Out the Repository

In addition to the XmlPL repository, you will also need the BasicUtils library from the XMLCereal project. You can attain these with the following commands.

mkdir xmlpl
cd xmlpl
svn co https://xmlcereal.svn.sourceforge.net/svnroot/xmlcereal/trunk/BasicUtils libbasicutils
svn co https://xmlpl.svn.sourceforge.net/svnroot/xmlpl/trunk .
		

4) Build & Install the Packages

The XmlPL compiler tools are made up of a number of packages. You must build and install these in the following order.

  • libbasicutils
  • libantlr
  • libxmlpl_cpp_runtime
  • xmlplcc
  • libxmlpl_cpp_standard
  • xmlpl

The packages can be built with the following commands.

cd <package directory>
./autogen.sh
./configure --prefix <install path>
make
make install
cd ..
		

If you want to install directly to your system paths then you may omit the --prefix <install path> option. Otherwise, you should ensure that <install path> is listed in your PATH environment variable so that the other packages can find their installed dependencies. You may also need to set your LD_LIBRARY_PATH. You can use the following commands to achieve this.

export PATH=$PATH:<install path>/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH=<install path>/lib
		

Of course you must replace <install path> with your actual install path.