<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html class="client-nojs" dir="ltr" lang="en">
<head>
<meta charset="UTF-8" />
<title>Documents/How to/Build from source - OpenSCADAWiki</title>
<meta content="MediaWiki 1.26.4" name="generator" />
<link href="https://www.gnu.org/copyleft/fdl.html" rel="copyright" />
<link href="files/doc.css" rel="stylesheet" /></head>
<body><div class="floatright"><a href="index.html"><img alt="OpenSCADA" src="../en/files/index.png" /></a></div><div id="mw_header">
<div class="mw-indicators">
</div>
<h1 id="firstHeading" lang="en">Documents/How to/Build from source</h1>
</div><div class="mw-content-ltr" dir="ltr" id="mw-content-text" lang="en"><div class="mw-pt-languages" dir="ltr" lang="en"><div class="mw-pt-languages-list autonym"><span class="mw-pt-languages-ui mw-pt-languages-selected mw-pt-progress mw-pt-progress--complete">English</span> • ‎<a class="mw-pt-progress mw-pt-progress--stub" href="../ru/How_to_Build_from_source.html" title="Документы/Как/Собрать из иÑходных текÑтов (19% translated)">mRussian</a> • ‎<a class="mw-pt-progress mw-pt-progress--complete" href="../uk/How_to_Build_from_source.html" title="Документи/Як/СклаÑти з вихідних текÑтів (100% translated)">УкраїнÑька</a></div></div>
<div style="float:right; border:1px solid gray; width:300px; padding:2px; margin-left: 10pt; margin-bottom: 10pt;">
<ul><li> <b>Author:</b> <a class="external" href="http://oscada.org/wiki/User:RomanSavochenko" title="User:RomanSavochenko">Roman Savochenko</a>, <a class="external text" href="http://oscada.org/en/forum/user/IrmIngeneer/" rel="nofollow noreferrer noopener" target="_blank">Constantine</a> </li></ul>
</div>
<p>The manual is intended to help in the building of OpenSCADA from source texts. In the process of accumulation of experience of building OpenSCADA for different OS Linux distributions and others platforms generally, the document will be appended by the features and details of the building in the environments.
</p><p>Pre-configuration of the built program on the latest versions of OpenSCADA is not required if used when building the "openscada-res" resource package or the source tree from the SVN repository, even after a direct build. Therefore, immediately after building and installation, the program is ready for use!
</p><p><a class="image" href="http://oscada.org/wiki/File:At.png"><img alt="At.png" height="22" src="files/At.png" width="22" /></a> Building OpenSCADA from source texts requires experience in building free software, as well as basic knowledge of the Linux OS and the used Linux distribution. That will allow you to correctly satisfy dependencies and solve possible building problems.
</p>
<div class="toc" id="toc"><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#OpenSCADA_configuration_for_building"><span class="tocnumber">1</span> <span class="toctext">OpenSCADA configuration for building</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Direct_building_of_OpenSCADA"><span class="tocnumber">2</span> <span class="toctext">Direct building of OpenSCADA</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#Building_of_OpenSCADA_packages_for_the_Linux_distribution"><span class="tocnumber">3</span> <span class="toctext">Building of OpenSCADA packages for the Linux distribution</span></a>
<ul>
<li class="toclevel-2 tocsection-4"><a href="#Debian-based_distributions_.E2.80.94_DEB_packages"><span class="tocnumber">3.1</span> <span class="toctext">Debian-based distributions — DEB packages</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#RedHat-based_distributions_.E2.80.94_RPM_packages"><span class="tocnumber">3.2</span> <span class="toctext">RedHat-based distributions — RPM packages</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#Gentoo_.E2.80.94_metadistribution"><span class="tocnumber">3.3</span> <span class="toctext">Gentoo — metadistribution</span></a></li>
<li class="toclevel-2 tocsection-7"><a href="#Lightweight_package_management_system_.E2.80.94_IPKG_packages"><span class="tocnumber">3.4</span> <span class="toctext">Lightweight package management system — IPKG packages</span></a></li>
<li class="toclevel-2 tocsection-8"><a href="#Building_for_Android_.E2.80.94_APK_packages"><span class="tocnumber">3.5</span> <span class="toctext">Building for Android — APK packages</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><span class="mw-headline" id="OpenSCADA_configuration_for_building"><span class="mw-headline-number">1</span> OpenSCADA configuration for building</span></h2>
<p>As a build system, the OpenSCADA project uses a set of utilities <a class="external text" href="http://en.wikipedia.org/wiki/GNU_build_system" rel="nofollow noreferrer noopener" target="_blank">AutoTools</a>. Any building of the project under the control of AutoTools is preceded by the configuration stage for the OS environment, and sometimes the formation of the building system itself. The configuration stage, as well as the direct building, is always carried out and does not depend on whether it is a direct building or a package building.
</p><p>AutoTools utilities <b>autoconf</b>, <b>automake</b> and <b>libtool</b> must be installed to create a building system. General formation can be done with the command <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">autoreconf -if</span>. A previously formed building system may sometimes need to be reformatted, for example, in the case of a significant difference between the OS environment of the formation and the current one! Reformation of the building system is also carried out by the previously defined formation command.
</p><p>The configuration of the building system is carried out by calling the <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure</span> command. By specifying arguments to this command, you can enable-disable an OpenSCADA function or module. You can get the entire list of available OpenSCADA configuration parameters and modules by specifying the <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --help</span> argument.
</p><p>OpenSCADA modules are enabled and disabled by passing the arguments <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --enable-{ModName} </span> and <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --disable-{ModName} </span>. When selecting modules, you can specify the policy "Enable all modules" — <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --enable-AllModuls</span> or "Disable all modules" — <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --disable-AllModuls</span>, and further enable-disable individual modules, whichever is easier. Most OpenSCADA modules can be linked (embedded) directly into the OpenSCADA core library, rather than being built as a separate library, for which the <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --enable-{ModName}=incl</span> argument must be specified.
</p><p>Generically you can build OpenSCADA in three binary configurations, operating the core library place by the argument <span style="border: solid gray 1px; padding: 1px; font-family: monospace; font-size: 1.2em; white-space: nowrap;">configure --enable-CoreLibStatic</span>:
</p>
<ol><li> Standard with the shared core library <b>lib/liboscada.so.4.0.9</b>, the shared module libraries <b>lib/openscada/{modTp}_{modNm}.so</b> and the starting binary <b>bin/openscada</b> — effective on big systems with starting many OpenSCADA projects and flexible control for loaded modules.</li>
<li> Without the shared core library, with the shared module libraries <b>lib/openscada/{modTp}_{modNm}.so</b> and the starting binary <b>bin/openscada</b> with statically builtin code of the core library — effective on systems with fast starting one or several OpenSCADA projects and flexible control for loaded modules.</li>
<li> All in one starting binary <b>bin/openscada</b> by statically building here code of the core library and all modules — effective on very tight embedded systems for embedding all need functions in maximum small single binary.</li></ol>
<p>Upon successful completion of the configuration, a summary result of the settings will be generated, with which you can check the main points.
</p><p>Before building, you need to decide on the source of the source texts, <a class="external text" href="http://oscada.org/en/main/download/" rel="nofollow noreferrer noopener" target="_blank">FTP/HTTP-server or SVN-repository</a>, and the branch of OpenSCADA that you will build. Since the LTS branch is automatically built for many Linux distributions, is rarely updated and its version changes with the release of a new LTS, this guide will consider the assembly of the working branch (Work), which, in turn, is automatically compiled for a limited range of Linux distributions, often changes and its address always the same, unless you count the revision number. As a rule, the building of the LTS branch is carried out in the same way, and in the instructions "Work" should be replaced with the LTS version and the name of the source text package should be changed. In general, the names of packages and folders should be treated carefully, because they can differ from version to version!
</p>
<h2><span class="mw-headline" id="Direct_building_of_OpenSCADA"><span class="mw-headline-number">2</span> Direct building of OpenSCADA</span></h2>
<p>Building must be done as a normal user, although for isolated environments it can also be done as a superuser. At the same time, variants for installation and execution will be considered both globally — in the system, and locally — in the user's folder. We accept the user's login (account) as "user".
</p><p>Log in as a normal user and replace the "user" account with yours, decide on the installation method (global or local) and follow the instructions:
</p><p>Steps of preparation the source tree for building:
</p>
<dl><dd>1. Make directory for the project building:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>mkdir ~/projects
<span class="nb">cd</span> ~/projects
</pre></div>
<dl><dd>2. Download the sources package. It may be made from two ways:
<ul><li> [TAR] download TAR archive from the FTP/HTTP-server <a class="external free" href="http://ftp.oscada.org/OpenSCADA/" rel="nofollow noreferrer noopener" target="_blank">http://ftp.oscada.org/OpenSCADA/</a> and unpack it, for example:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>wget http://ftp.oscada.org/OpenSCADA/Work/openscada-1+r2920.tar.xz
wget http://ftp.oscada.org/OpenSCADA/Work/openscada-res-1+r2920.tar.xz
tar -xvf openscada-1+r2920.tar.xz
<span class="nb">cd </span>openscada-1+r2920
tar -xvf ../openscada-res-1+r2920.tar.xz
</pre></div>
<dl><dd><ul><li> [SVN] obtain the project source tree from the SVN-repository:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>svn co http://oscada.org/svn/trunk/OpenSCADA/
<span class="nb">cd </span>OpenSCADA
</pre></div>
<dl><dd>3. Resolve the OpenSCADA dependencies for the building, in accordance to <a href="Functions_and_demands.html#Building" title="Special:MyLanguage/Functions and demands">the demands</a>.</dd>
<dd>4. [SVN] Generate of the building system, when download from the SVN-repository:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>autoreconf -ivf
</pre></div>
<p>Steps of the global building:
</p>
<dl><dd>1. Configure the building system of OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>./configure
</pre></div>
<dl><dd>2. Build OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>make
</pre></div>
<dl><dd>3. Install OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>su <span class="c"># Entry for superuser</span>
make install
</pre></div>
<dl><dd>5. The program is ready to start up:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre><span class="nb">exit</span>
openscada
</pre></div>
<p>Steps of the local building:
</p>
<dl><dd>1. Configure the building system of OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>mkdir ~/OScadaW
./configure --prefix<span class="o">=</span>/home/user/OScadaW
</pre></div>
<dl><dd>2. Build OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>make
</pre></div>
<dl><dd>3. Install OpenSCADA:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre>make install
</pre></div>
<dl><dd>4. The program is ready to start up:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 20px"><pre><span class="nb">cd</span> ~/OScadaW/bin
./openscada
</pre></div>
<h2><span class="mw-headline" id="Building_of_OpenSCADA_packages_for_the_Linux_distribution"><span class="mw-headline-number">3</span> Building of OpenSCADA packages for the Linux distribution</span></h2>
<h3><span class="mw-headline" id="Debian-based_distributions_.E2.80.94_DEB_packages"><span class="mw-headline-number">3.1</span> Debian-based distributions — DEB packages</span></h3>
<p>In order to build OpenSCADA DEB packages, you will need archives of source texts and resources.
</p><p>Building of DEB packages is located in the "debian" folder with build scripts contained in archives of the OpenSCADA source texts.
</p><p>Building steps:
</p>
<dl><dd>1. Create a directory to build the program:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>mkdir ~/build
<span class="nb">cd</span> ~/build
</pre></div>
<dl><dd>2. Download the sources packages. It may be made from two ways:
<ul><li> [TAR] download TAR archive from the FTP/HTTP-server <a class="external free" href="http://ftp.oscada.org/OpenSCADA/" rel="nofollow noreferrer noopener" target="_blank">http://ftp.oscada.org/OpenSCADA/</a> and unpack it, for example:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>wget http://ftp.oscada.org/OpenSCADA/Work/openscada-1+r2920.tar.xz
wget http://ftp.oscada.org/OpenSCADA/Work/openscada-res-1+r2920.tar.xz
tar -xvf openscada-1+r2920.tar.xz
<span class="nb">cd </span>openscada-1+r2920
tar -xvf ../openscada-res-1+r2920.tar.xz
</pre></div>
<dl><dd><ul><li> [SVN] obtain the project source tree from the SVN-repository:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>svn co http://oscada.org/svn/trunk/OpenSCADA/
<span class="nb">cd </span>OpenSCADA
</pre></div>
<dl><dd>3. Selection the building type:
<ul><li> binary files in one package:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>ln -s data/debian debian
</pre></div>
<dl><dd><ul><li> binary modules files in separate packages:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>ln -s data/debian_mod debian
</pre></div>
<dl><dd>4. Resolve the OpenSCADA dependencies for the building, in accordance to <a href="Functions_and_demands.html#Building" title="Special:MyLanguage/Functions and demands">the demands</a>. Arguments for the command "configure" you can specify into the file "debian/rules".</dd>
<dd>5. Building:
<ul><li> build from the beginning:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>dpkg-buildpackage -rfakeroot
</pre></div>
<dl><dd><ul><li> skip the building and repack, it is convenient for the debugging "debian/rules":</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>fakeroot debian/rules binary
fakeroot debian/rules build
</pre></div>
<dl><dd>6. Packages are ready and available in the level above directory.</dd></dl>
<h3><span class="mw-headline" id="RedHat-based_distributions_.E2.80.94_RPM_packages"><span class="mw-headline-number">3.2</span> RedHat-based distributions — RPM packages</span></h3>
<p>For building OpenSCADA RPM packages, you will need source texts archives, resources, and a RPM package specification file (<a class="external text" href="http://oscada.org/svn/trunk/OpenSCADA/data/" rel="nofollow noreferrer noopener" target="_blank">openscada.spec, openscada_mod_ALT.spec, openscada_mod_RH.spec</a>), or a SRPM package of all these source materials.
</p><p>The RPM package specification file and the SRPM package may differ for different Linux distributions, taking into account their features, so you should try to load them according to the distribution. If there is no special SRPM packet then you can try to build from the unified specification file (openscada.spec) in the main SRPM package or resource packet.
</p><p>Building the RPM packages takes place in a directory with a special structure that is usually created when installing the appropriate distribution package (as "rpm-build"). This directory, depending on the distribution, is located in the user's home directory or in the "/usr/src" directory. Known facts of location of the directory <i>RPMBuildDir</i> of RPM Packages of different distributions:
</p>
<ul><li> "~/rpmbuild" — <a class="external text" href="https://www.redhat.com" rel="nofollow noreferrer noopener" target="_blank">RedHat</a>, <a class="external text" href="https://www.centos.org/" rel="nofollow noreferrer noopener" target="_blank">CentOS</a>, Mandriva, <a class="external text" href="http://fedoraproject.org" rel="nofollow noreferrer noopener" target="_blank">Fedora</a></li>
<li> "/usr/src/packages" — <a class="external text" href="https://www.opensuse.org/" rel="nofollow noreferrer noopener" target="_blank">SuSE</a></li>
<li> "~/RPM" — <a class="external text" href="http://altlinux.com" rel="nofollow noreferrer noopener" target="_blank">ALTLinux</a></li></ul>
<p>If you have no directory of RPM packets after installing the specialized package, then you need to create it with the command:
</p>
<div class="mw-highlight mw-content-ltr" dir="ltr"><pre>install -m <span class="m">755</span> -d ~/rpmbuild/<span class="o">{</span>SPECS,SOURCES<span class="o">}</span> <span class="c"># RedHat, CentOS, Mandriva, Fedora</span>
install -m <span class="m">755</span> -d /usr/src/packages/<span class="o">{</span>SPECS,SOURCES<span class="o">}</span> <span class="c"># SuSE</span>
install -m <span class="m">755</span> -d ~/RPM/<span class="o">{</span>SPECS,SOURCES<span class="o">}</span> <span class="c"># ALTLinux</span>
</pre></div>
<p>Building steps at the RPM specification file:
</p>
<dl><dd>1. Locate the OpenSCADA archives and the specification file in the RPM build folder (the source files are pre-located in the current directory):</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>cp openscada-1+r2920.tar.xz openscada-res-1+r2920.tar.xz <span class="o">{</span>RPMBuildDir<span class="o">}</span>/SOURCES
cp openscada.spec <span class="o">{</span>RPMBuildDir<span class="o">}</span>/SPECS
</pre></div>
<dl><dd>2. Resolve of the OpenSCADA project's dependencies for building in accordance with <a href="Functions_and_demands.html#Building" title="Special:MyLanguage/Functions and demands">the requirements</a>. Arguments for the command "configure" you can specify into the file "openscada.spec".</dd>
<dd>3. Build the packages
<ul><li> build from the beginning:</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>rpmbuild -bb <span class="o">{</span>RPMBuildDir<span class="o">}</span>/SPECS/openscada.spec
</pre></div>
<dl><dd><ul><li> only the installation and packaging from the etersoft rpm-utilities package (useful when configuring openscada.spec file):</li></ul></dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>rpmbb -i <span class="o">{</span>RPMBuildDir<span class="o">}</span>/SPECS/openscada.spec
</pre></div>
<dl><dd>4. Packages are ready and available in the directory "{RPMBuildDir}/RPMS" for the appropriate architecture.</dd></dl>
<p>Building steps for the SRPMS package:
</p>
<dl><dd>1. Resolve of the OpenSCADA project's dependencies for building in accordance with <a href="Functions_and_demands.html#Building" title="Special:MyLanguage/Functions and demands">the requirements</a>.</dd>
<dd>2. Build of the packages (the source files pre-placed in the current directory):</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>rpmbuild --rebuild openscada-1+r2920.src.rpm
</pre></div>
<dl><dd>3. Packages are ready and available in the directory "{RPMBuildDir}/RPMS" for the appropriate architecture.</dd></dl>
<h3><span class="mw-headline" id="Gentoo_.E2.80.94_metadistribution"><span class="mw-headline-number">3.3</span> Gentoo — metadistribution</span></h3>
<p>OpenSCADA is not included to the official portage Gentoo tree, so the building is made from the overlay. Before the building of the OpenSCADA package itself, portage will satisfy dependencies, ie build the missing packages (if necessary).
</p>
<dl><dd>1. Create an overlay "portage" by description of the path for an overlay tree, that is, in "/etc/make.conf" you need to write a line</dd></dl>
<pre style="margin-left: 40px">
PORTDIR_OVERLAY="/usr/local/portage"
</pre>
<dl><dd>2. Create a directory "/usr/local/portage/dev-util/openscada/", then download the ebuild archive file from the official site and unpack it in the created folder.</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre><span class="nb">cd</span> /usr/local/portage/dev-util/openscada
wget http://ftp.oscada.org/OpenSCADA/LTS/Gentoo/openscada-0.9.4.ebuild.tar.bz2
tar -xvf openscada-0.9.4.ebuild.tar.bz2
</pre></div>
<dl><dd>3. You must specify the portage, that OpenSCADA is allowed to build on your platform. To do this, put the following line to the file "/etc/portage/package.keywords":</dd></dl>
<pre style="margin-left: 40px">
dev-util/openscada
</pre>
<dl><dd>4. Check:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>emerge -vp openscada
</pre></div>
<pre style="margin-left: 50px">
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] dev-util/openscada-0.9 USE="mysql ssl -bfn -blockcalc -daqgate -dbarch -dbase -dcon -demo -diamondboards -doc (-firebird)
-flibcomplex1 -flibmath -flibsys -fsarch -http -icp_das -javalikecalc -logiclev -modbus -portaudio -qtcfg -qtstarter -selfsystem
-serial -simens -snmp -sockets -sqlite -system -systemtest -vcaengine -vision -webcfg -webcfgd -webvision" 79,647 kB [1]
Total: 1 package (1 reinstall), Size of downloads: 79,647 kB
Portage tree and overlays:
[0] /usr/portage
[1] /usr/local/portage
</pre>
<dl><dd>5. If you have no connection to Internet, you have to download the sources and resources tarballs from FTP/HTTP-server of the project and place them in advance in the sources directory of the portage "/usr/portage/distfiles". If you have an Internet connection, then everything that is necessary for building will be taken from the project's server automatically.</dd>
<dd>6. It is necessary to put the required USE-flags, with which the OpenSCADA will be built. This can be done in the file "/etc/portage/package.use", for example:</dd></dl>
<pre style="margin-left: 40px; white-space: normal">
dev-util/openscada dcon demo http javalikecalc mysql qtcfg qtstarter ssl vision webcfg webcfgd webvision blockcalc dbarch dbase doc flibcomplex1 flibmath flibsys fsarch logiclev modbus serial sockets sqlite vcaengine
</pre>
<dl><dd>7. Build:</dd></dl>
<div class="mw-highlight mw-content-ltr" dir="ltr" style="margin-left: 40px"><pre>emerge -q openscada
</pre></div>
<dl><dd>8. Database files and resources of OpenSCADA are ready and placed in the directory "/var/spool/openscada/", executable files — "/usr/bin/", documentation — "/usr/share/doc/openscada-0.9/".</dd></dl>
<h3><span class="mw-headline" id="Lightweight_package_management_system_.E2.80.94_IPKG_packages"><span class="mw-headline-number">3.4</span> Lightweight package management system — IPKG packages</span></h3>
<p>An area of application of the package manager and packages IPKG has builtin Linux environments with limited amount of memory, such as wireless routers. Accordingly, the building of IPKG packages is a part of the build systems of such environments and the description of this procedure can not be considered separately from the build system itself, so for the creation of IPKG packages of OpenSCADA read in the section "<a class="external" href="http://oscada.org/wiki/Special:MyLanguage/Sub-projects/Embedding_and_PLC#OpenWrt" title="Special:MyLanguage/Sub-projects/Embedding and PLC">OpenWrt distributive</a> of the subproject <a class="external" href="http://oscada.org/wiki/Special:MyLanguage/Sub-projects/Embedding_and_PLC" title="Special:MyLanguage/Sub-projects/Embedding and PLC">OpenSCADA generic embedding and programmable logical controllers (PLC)</a>".
</p>
<h3><span class="mw-headline" id="Building_for_Android_.E2.80.94_APK_packages"><span class="mw-headline-number">3.5</span> Building for Android — APK packages</span></h3>
<p>The operating system <a class="external text" href="https://en.wikipedia.org/wiki/Android_(operating_system)" rel="nofollow noreferrer noopener" target="_blank">Android</a> is a Linux-kernel based software that is primarily designed and used on mobile phones, smartphones, tablets, and other touch-screened devices. The third-party software for Android is distributed in the form of APK-packages, the building of which can not be considered apart from the build environment of the Android SDK, NDK and building of all dependencies of OpenSCADA, so read on the subject of the building of OpenSCADA and the creation of its APK-packages in the sub-project "<a class="external" href="http://oscada.org/wiki/Special:MyLanguage/Sub-projects/Adaption_to_Android" title="Special:MyLanguage/Sub-projects/Adaption to Android">OpenSCADA adaption to the software platform Android</a>".
</p>
</div><table style="border-top: dotted 2px #999999; margin-top: 20pt; color: gray;" width="100%"><tr><td style="text-align: left;" width="40%"><a href="http://oscada.org/wiki/Documents/How_to/Build_from_source/en">Documents/How_to/Build_from_source/en</a> - <a href="http://oscada.org/en/main/about-the-project/licenses/">GFDL</a></td><td style="text-align: center;">April 2025</td><td style="text-align: right;" width="40%">OpenSCADA 1+r3018</td></tr></table></body>
</html>