Compile on Linux

Previous: Licence

Next: Compile on Linux

Index

This page explains step by step how to compile LabRPS 0.001 or newer on Linux. For other platforms see Compiling.

Prerequisites

Compiling LabRPS on Linux requires several tools and libraries.

• A compiler. LabRPS is tested with MinGW—other compilers may work, but instructions for their use are not included here. More details in #Compiler, below.

• Qt for C++ (>=4.3).

• Qwt (>=5.1.0).

• QwtPlot3D (>=0.2.6).

• GSL (>=1.8).

• muParser (>=1.28).

• zlib (>=1.2.3).

QwtPlot3D and Qwt must be compiled against Qt 5.x! If these are compiled with Qt3 or Qt4, the application might crash.

Source code

Now you can get the source code of LabRPS:

Using a frontend

When using the Git frontend TortoiseGit:

1. Create a new folder where the source code will be downloaded.
2. Right-click on this folder in the Windows file explorer and select Git Clone in the context menu.
3. A dialog will appear. In it, enter the URL for the LabRPS Git repository

https://github.com/LabRPS/LabRPS.git

and click OK.

The latest source code will be downloaded from the LabRPS Git repository and the folder will be tracked by Git.

Using the command line

To create a local tracking branch and download the source code, open a terminal (command prompt) and switch there to the directory you want the source, then type:

git clone https://github.com/LabRPS/LabRPS.git

Building LabRPS

1. Install Qt(>=4.3), GSL, muParser and zlib; either from your package manager or from the sources. If you are using precompiled packages, make sure you also install the corresponding development packages (*-dev or *-devel). If you want to display the manual from within LabRPS (you can also view it with your favorite browser), you need to have the Qt Assistant installed, which sometimes comes in a separate package (qt4-dev-tools for Ubuntu edgy).
2. Open a terminal window.
3. Get Qwt (>=5.1.0) sources and unpack them to the 3rdparty folder:

 LabRPS-X.X.X/3rdparty tar -xvjf /path/to/qwt-Y.Y.Y.tar.bz2}}

4. Rename the new directory to

   qwt:

mv qwt-Y.Y.Y qwt

5. We want to build the static version of Qwt in order to avoid potential conflicts with an already installed version. Open the file qwt/qwtconfig.pri and comment out the line

CONFIG += QwtDll

6. Build Qwt:

cd qwt; qmake && make; cd ..

On some systems (such as Debian, Ubuntu, ...) the

qmake

-Tool for Qt 4.x is called

qmake-qt4

. Make sure you don't use the version that belongs to Qt 3.x.
7. Get QwtPlot3D sources and also unpack them to LabRPS-X.X.X/3rdparty:

tar -xvzf qwtplot3d-Z.Z.Z.tgz

8. We also want to build a static version here, so open qwtplot3d/qwtplot3d.pro in your favorite text editor and add the line

CONFIG += staticlib

   at a convenient place (say, below the other CONFIG line).

9. Build qwtplot3d:

cd qwtplot3d; qmake && make; cd ..

10. Go to the directory LabRPS-X.X.X/LabRPS:

cd ../LabRPS

11. If you want to use Python expressions and scripts, make sure you have the following additional dependencies installed: Python (>=2.5), SIP (>=4.6), PyQt (>=4.2). Other versions as those indicated above may or may not work. Specifically, there are known issues with a number of SIP versions and a given version of PyQt will only work with a limited range of SIP versions. Open LabRPS.pro in a text editor and remove the comment marker (#) from the line

    include( python.pri ).

12. Build LabRPS:

qmake && make

13. You should now be able to run LabRPS by entering

./LabRPS

14. Optionally, install LabRPS on your system (you need root priviliges):

sudo make install

or, alternatively,

su -c "make install"

Additional information

1. Forums and mailing lists If you want to discuss LabRPS with other users (or the developers) or if you are insterested in its further development, you can go to the LabRPS forum.
2. License LabRPS is distributed under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. A copy of this license is provided in the file `gpl.txt`.

Thus it is "free software". "Free software" is a matter of liberty, not price. To understand the concept, you should think of "free" as in "free speech", not as in "free beer". "Free software" is also often called Open Source, FOSS, or FLOSS. When we say that LabRPS is "free", we are talking about

• The freedom to run the program, for any purpose (freedom 0).
• The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
• The freedom to redistribute copies so you can help your neighbor (freedom 2).
• The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.

That said, LabRPS is also free as in "free beer". We do not charge money for anything you can download on our homepage and we will not do so in the future. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Previous: Licence

Next: Compile on Linux

Index

User documentation

• Getting started
• Installation: Download, Windows, Linux, Mac, Additional components, AppImage
• Basics: About LabRPS, Interface, RPS Objects, Object name, Preferences, Workbenches, Document structure, Properties, Help LabRPS, Donate

---

• Help: Tutorials, Video tutorials
• Workbenches: Std Base, WindLab, SeismicLab, SeaLab, Spreadsheet

---

• Addons: Addon Manager, Plugins, Scripting and macros

---

• Hubs: User hub, Power users hub, Developer hub