Compile alternatives for source Packages in Pisi Linux

When you will compile forget not, install the build-essentials with the command

sudo pisi it -c system.devel

without it you can not compile packages

The configure script

A configure script is an executable script designed to aid in developing a program to be run on a wide number of different computers. It matches the libraries on the user’s computer, with those required by the program before compiling it from its source code.

As a common practice, all configure scripts are named “configure”. Usually, configure scripts are written for the Bourne shell, but they may be written for execution in any desired shell.


Obtaining software directly from the source code is a common procedure on Unix computers, and generally involves the following three steps: configuring the makefile, compiling the code, and finally installing the executable to standard locations. A configure script accomplishes the first of these steps. Using configure scripts is an automated method of generating makefiles before compilation to tailor the software to the system on which the executable is to be compiled and run. The final executable software is most commonly obtained by executing the following commands in a shell that is currently pointing to the directory containing the source code:

make install (for a system wide installation you must type sudo )

One must type ./configure rather than simply configure to indicate to the shell that the script is in the current directory. By default, for security reasons, Unix operating systems do not search the current directory for executables so one must give the full path explicitly to avoid an error.

Upon its completion, configure prints a report to config.log. Running ./configure --help gives a list of command line arguments, for enabling or disabling additional features such as:
./configure --libs="-lmpfr -lgmp"
./configure --prefix=/home/myname/apps
./configure --prefix=Path
The first line includes the mpfr and gmp libraries.

The second line tells make to install the final version in /home/myname/apps. The INSTALL file contains instructions should the prescribed steps fail.


For the compiling with cmake read this one:



Programs that are written in Qt are created with qmake. These must be available to compile or create a <program name> .pro file with the information.

With the commands
qmake-qt4 <programmname>.pro
qmake-qt5 <programmname>.pro

or only with

Last but not least

Installation scripts

Programs in different scripting languages such as Python, Ruby, Perl, Java etc, have the most time installation scripts. Such programs do not have to be compiled and the scripts take only task is to copy the files to the right place to make the program available systemwide. Something like this is also true for precompiled programs.

Two examples with reference at a shell and a Python script:

python install

You have now a little overview about compiling, but recommendable is all Times takes the Programs from your Repository, compiling is not so hard try it and you will so much more you compile so easier goes it.