Up to version 2.0 the source code was maintained in a Subversion repository.
Currently the code is maintained in a Git repository. The complete commit history has been migrated to git.
Currently the code is maintained in a Git repository. The complete commit history has been migrated to git.
To work with the code from the repository, follow the steps below.
Steps 2 and 3 are the main difference with the build process from a source code distribution.
- Your machine will need the following software components in addition to the ones listed for compiling from a distribution file:
- 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 the different *nix flavors. - 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. - doxygen, any version should do
Extracts documentation from the C++ source code. - wget
Command line HTTP client. - git
Distributed version control tool.
- autoconf, v2.59 or later
- Pick up the latest code from the repository with the command:
git clone git://git.code.sf.net/p/frepple/git <project_directory>
or
git clone https://github.com/jdetaeye/frePPLe.git <project_directory>
Both of these repositories are kept up to date.
- Initialize the automake/autoconf/libtool scripts:
cd <project_directory> make -f Makefile.dist prep
- Now the configure script is up to date and you can follow the same steps as in this section to compile the code.
- To sync your environment with the latest changes from the repository:
cd <project_directory> git pull