This page is a bit old!

Click here to look at the most recent version of this page.

Compiling on Linux

This page describes 3 different methods:

The instructions on this page describe how you compile the frePPLe source code into binaries. After compilation you need to return to the installation and configuration steps outlined on the previous page.

Compiling from the github source code repository or source tarball

To work with the source code directly from the github repository you will need the following steps:

  1. Update your system with the development software packages.

    • gcc, v3.4 or higher
      Front end for the GNU compiler suite.
    • gcc-c++, compatible with gcc release
      GNU C++ compiler.
    • xerces-c, 3.0 or 3.1
      Xerces is a validating XML parser provided by the Apache Foundation.
      You need to install the libraries as well as the development libraries.
    • python 3.4 or higher
      Python is a modern, easy to learn interpreted programming language.
      You need to install the language as well as the development libraries.
    • git
      Distributed version control tool.
    • autoconf, v2.59 or later
      Gnu Autoconf produces shell scripts to automatically configure software source code packages. This makes the source code easier to port across platforms.
    • automake, v1.9.5 or later
      Gnu Automake is a tool for automatically generating make-files.
    • libtool, v1.5 or later
      Libtool hides the complexity of developing and using shared libraries for different platforms behind a consistent and portable interface.
    • python-sphinx (optional)
      A modern documentation generation tool.
  2. Pick up the latest code from the repository with the command:

    git clone <project_directory>
  3. Initialize the automake/autoconf/libtool scripts:

    cd <project_directory>
    make -f Makefile.dist prep
  4. Configure the build with the following command:

    ./configure --sysconfdir=/etc

    You can use the option ‘–help’ to see the list of available options.

    The sysconfdir option is required to make sure the configuration files are always available under /etc, even when the package is compiled with a prefix such as /usr/local.

  5. Compile the source code:

    make all
  6. Run the test suite:

    make check

    Not all tests are currently passing, so you shouldn’t be worried about a couple of failures.

  7. Install the files:

    make install
  8. Free the disk space used during the build and test phases.

    make clean
  9. To sync your environment with the latest changes from the repository:

    cd <project_directory>
    git pull
  10. Example Suse Enterprise 12 SP1 build script to create RPMs:

    export GITURL=""
    export GITBRANCH=master
    # Basics
    sudo zypper update
    sudo zypper --non-interactive install --force-resolution libxerces-c-3_1 libxerces-c-devel openssl openssl-devel libtool make automake autoconf doxygen python3 python3-devel gcc-c++ graphviz rpm-build git libpq5 postgresql-devel
    #create rpm tree
    mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
    # GIT
    git clone $GITURL -b $GITBRANCH frepple-$RELEASE/
    # PIP and PIP requirements
    sudo python3 -m ensurepip
    sudo pip3 install -r ~/frepple-$RELEASE/requirements.txt
    sudo pip3 install psycopg2 Sphinx
    cd ~/frepple-$RELEASE
    make -f Makefile.dist prep config
    cd contrib/rpm
    make suse

Compiling from a debian source package

The steps to work with such packages are standard:

  1. Install the django package as described on the previous page.

  2. Install the dpkg-dev package and all prerequisite packages for frepple:

    apt-get install dpkg-dev debhelper cdbs autotools-dev python-dev libxerces-c-dev libtool python-sphinx
  3. Build the source directory.

    Expand all files listed in the .dsc file.

  4. Build the package in the source directory.

    dpkg-buildpackage -B

Compiling from a RPM source package

The steps to work with such packages are standard:

  1. Install the django package as described on the previous page.

  2. Install the rpmbuild package:

    dnf install rpmbuild
    zypper in rpmbuild
  3. Create a build directory structure:

    mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
  4. Install the source RPM file:

    This will create files in the SOURCES directory of your RPM building directory tree, and a .spec file in the SPECS directory.

    rpm -i frepple-*.src.rpm
  5. Build the RPM:

    Go the SPECS directory and give the command to build the RPM:

    cd /home/your_userid/rpm/SPECS
    rpmbuild -bb frepple.spec