building.rst 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300
  1. .. _building:
  2. Building open62541
  3. ==================
  4. open62541 uses CMake to build the library and binaries. The library version is automatically
  5. detected using ``git describe``. This command returns a valid version string based on the current tag.
  6. If you did not directly clone the sources, but use the tar or zip package from a release, you need
  7. to manually specify the version. In that case use e.g. ``cmake -DOPEN62541_VERSION=v1.0.3``.
  8. Building the Library
  9. --------------------
  10. Building with CMake on Ubuntu or Debian
  11. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  12. .. code-block:: bash
  13. sudo apt-get install git build-essential gcc pkg-config cmake python
  14. # enable additional features
  15. sudo apt-get install cmake-curses-gui # for the ccmake graphical interface
  16. sudo apt-get install libmbedtls-dev # for encryption support
  17. sudo apt-get install check libsubunit-dev # for unit tests
  18. sudo apt-get install python-sphinx graphviz # for documentation generation
  19. sudo apt-get install python-sphinx-rtd-theme # documentation style
  20. cd open62541
  21. mkdir build
  22. cd build
  23. cmake ..
  24. make
  25. # select additional features
  26. ccmake ..
  27. make
  28. # build documentation
  29. make doc # html documentation
  30. make doc_pdf # pdf documentation (requires LaTeX)
  31. Building with CMake on Windows
  32. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  33. Here we explain the build process for Visual Studio (2013 or newer). To build
  34. with MinGW, just replace the compiler selection in the call to CMake.
  35. - Download and install
  36. - Python 2.7.x (Python 3.x works as well): https://python.org/downloads
  37. - CMake: http://www.cmake.org/cmake/resources/software.html
  38. - Microsoft Visual Studio: https://www.visualstudio.com/products/visual-studio-community-vs
  39. - Download the open62541 sources (using git or as a zipfile from github)
  40. - Open a command shell (cmd) and run
  41. .. code-block:: bat
  42. cd <path-to>\open62541
  43. mkdir build
  44. cd build
  45. <path-to>\cmake.exe .. -G "Visual Studio 14 2015"
  46. :: You can use use cmake-gui for a graphical user-interface to select features
  47. - Then open :file:`build\open62541.sln` in Visual Studio 2015 and build as usual
  48. Building on OS X
  49. ^^^^^^^^^^^^^^^^
  50. - Download and install
  51. - Xcode: https://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12
  52. - Homebrew: http://brew.sh/
  53. - Pip (a package manager for python, may be preinstalled): ``sudo easy_install pip``
  54. - Run the following in a shell
  55. .. code-block:: bash
  56. brew install cmake
  57. pip install sphinx # for documentation generation
  58. pip install sphinx_rtd_theme # documentation style
  59. brew install graphviz # for graphics in the documentation
  60. brew install check # for unit tests
  61. Follow Ubuntu instructions without the ``apt-get`` commands as these are taken care of by the above packages.
  62. Building on OpenBSD
  63. ^^^^^^^^^^^^^^^^^^^
  64. The procedure below works on OpenBSD 5.8 with gcc version 4.8.4, cmake version 3.2.3 and Python version 2.7.10.
  65. - Install a recent gcc, python and cmake:
  66. .. code-block:: bash
  67. pkg_add gcc python cmake
  68. - Tell the system to actually use the recent gcc (it gets installed as egcc on OpenBSD):
  69. .. code-block:: bash
  70. export CC=egcc CXX=eg++
  71. - Now procede as described for Ubuntu/Debian:
  72. .. code-block:: bash
  73. cd open62541
  74. mkdir build
  75. cd build
  76. cmake ..
  77. make
  78. .. _build_options:
  79. Build Options
  80. -------------
  81. The open62541 project uses CMake to manage the build options, for code
  82. generation and to generate build projects for the different systems and IDEs.
  83. The tools *ccmake* or *cmake-gui* can be used to graphically set the build
  84. options.
  85. Most options can be changed manually in :file:`ua_config.h` (:file:`open62541.h`
  86. for the single-file release) after the code generation. But usually there is no
  87. need to adjust them.
  88. Main Build Options
  89. ^^^^^^^^^^^^^^^^^^
  90. **CMAKE_BUILD_TYPE**
  91. - ``RelWithDebInfo`` -O2 optimization with debug symbols
  92. - ``Release`` -O2 optimization without debug symbols
  93. - ``Debug`` -O0 optimization with debug symbols
  94. - ``MinSizeRel`` -Os optimization without debug symbols
  95. **UA_LOGLEVEL**
  96. The SDK logs events of the level defined in ``UA_LOGLEVEL`` and above only.
  97. The logging event levels are as follows:
  98. - 600: Fatal
  99. - 500: Error
  100. - 400: Warning
  101. - 300: Info
  102. - 200: Debug
  103. - 100: Trace
  104. Select build artefacts
  105. ^^^^^^^^^^^^^^^^^^^^^^
  106. By default only the main library shared object libopen62541.so (open62541.dll)
  107. or static linking archive open62541.a (open62541.lib) is built. Additional
  108. artifacts can be specified by the following options:
  109. **UA_BUILD_EXAMPLES**
  110. Compile example servers and clients from :file:`examples/*.c`.
  111. **UA_BUILD_UNIT_TESTS**
  112. Compile unit tests. The tests can be executed with ``make test``
  113. **UA_BUILD_SELFSIGNED_CERTIFICATE**
  114. Generate a self-signed certificate for the server (openSSL required)
  115. Detailed SDK Features
  116. ^^^^^^^^^^^^^^^^^^^^^
  117. **UA_ENABLE_SUBSCRIPTIONS**
  118. Enable subscriptions
  119. **UA_ENABLE_SUBSCRIPTIONS_EVENTS (EXPERIMENTAL)**
  120. Enable the use of events for subscriptions. This is a new feature and currently marked as EXPERIMENTAL.
  121. **UA_ENABLE_METHODCALLS**
  122. Enable the Method service set
  123. **UA_ENABLE_NODEMANAGEMENT**
  124. Enable dynamic addition and removal of nodes at runtime
  125. **UA_ENABLE_AMALGAMATION**
  126. Compile a single-file release into the files :file:`open62541.c` and :file:`open62541.h`. Not recommended for installation.
  127. **UA_ENABLE_MULTITHREADING (EXPERIMENTAL)**
  128. Enable multi-threading support. Work is distributed to a number of worker threads.
  129. This is a new feature and currently marked as EXPERIMENTAL.
  130. **UA_ENABLE_IMMUTABLE_NODES**
  131. Nodes in the information model are not edited but copied and replaced. The
  132. replacement is done with atomic operations so that the information model is
  133. always consistent and can be accessed from an interrupt or parallel thread
  134. (depends on the node storage plugin implementation). This feature is a
  135. prerequisite for ``UA_ENABLE_MULTITHREADING``.
  136. **UA_ENABLE_COVERAGE**
  137. Measure the coverage of unit tests
  138. **UA_ENABLE_DISCOVERY**
  139. Enable Discovery Service (LDS)
  140. **UA_ENABLE_DISCOVERY_MULTICAST**
  141. Enable Discovery Service with multicast support (LDS-ME)
  142. **UA_ENABLE_DISCOVERY_SEMAPHORE**
  143. Enable Discovery Semaphore support
  144. **UA_NAMESPACE_ZERO**
  145. Namespace zero contains the standard-defined nodes. The full namespace zero
  146. may not be required for all applications. The selectable options are as follows:
  147. - ``MINIMAL``: A barebones namespace zero that is compatible with most
  148. clients. But this namespace 0 is so small that it does not pass the CTT
  149. (Conformance Testing Tools of the OPC Foundation).
  150. - ``REDUCED``: Small namespace zero that passes the CTT.
  151. - ``FULL``: Full namespace zero generated from the official XML definitions.
  152. The advanced build option ``UA_FILE_NS0`` can be used to override the XML
  153. file used for namespace zero generation.
  154. Some options are marked as advanced. The advanced options need to be toggled to
  155. be visible in the cmake GUIs.
  156. **UA_ENABLE_TYPENAMES**
  157. Add the type and member names to the UA_DataType structure. Enabled by default.
  158. **UA_ENABLE_STATUSCODE_DESCRIPTIONS**
  159. Compile the human-readable name of the StatusCodes into the binary. Enabled by default.
  160. **UA_ENABLE_FULL_NS0**
  161. Use the full NS0 instead of a minimal Namespace 0 nodeset
  162. ``UA_FILE_NS0`` is used to specify the file for NS0 generation from namespace0 folder. Default value is ``Opc.Ua.NodeSet2.xml``
  163. Debug Build Options
  164. ^^^^^^^^^^^^^^^^^^^
  165. This group contains build options mainly useful for development of the library itself.
  166. **UA_DEBUG**
  167. Enable assertions and additional definitions not intended for production builds
  168. **UA_DEBUG_DUMP_PKGS**
  169. Dump every package received by the server as hexdump format
  170. Building a shared library
  171. ^^^^^^^^^^^^^^^^^^^^^^^^^
  172. open62541 is small enough that most users will want to statically link the
  173. library into their programs. If a shared library (.dll, .so) is required, this
  174. can be enabled in CMake with the ``BUILD_SHARED_LIBS`` option. Note that this
  175. option modifies the :file:`ua_config.h` file that is also included in
  176. :file:`open62541.h` for the single-file distribution.
  177. Minimizing the binary size
  178. ^^^^^^^^^^^^^^^^^^^^^^^^^^
  179. The size of the generated binary can be reduced considerably by adjusting the
  180. build configuration. With open2541, it is possible to configure minimal servers
  181. that require less than 100kB of RAM and ROM.
  182. The following options influence the ROM requirements:
  183. First, in CMake, the build type can be set to ``CMAKE_BUILD_TYPE=MinSizeRel``.
  184. This sets the compiler flags to minimize the binary size. The build type also
  185. strips out debug information. Second, the binary size can be reduced by removing
  186. features via the build-flags described above.
  187. Second, setting ``UA_NAMESPACE_ZERO`` to ``MINIMAL`` reduces the size of the
  188. builtin information model. Setting this option can reduce the binary size by
  189. half in some cases.
  190. Third, some features might not be needed and can be disabled to reduce the
  191. binary footprint. Examples for this are Subscriptions or encrypted
  192. communication.
  193. Last, logging messages take up a lot of space in the binary and might not be
  194. needed in embedded scenarios. Setting ``UA_LOGLEVEL`` to a value above 600
  195. (``FATAL``) disables all logging. In addition, the feature-flags
  196. ``UA_ENABLE_TYPENAMES`` and ``UA_ENABLE_STATUSCODE_DESCRIPTIONS`` add static
  197. information to the binary that is only used for human-readable logging and
  198. debugging.
  199. The RAM requirements of a server are mostly due to the following settings:
  200. - The size of the information model
  201. - The number of connected clients
  202. - The configured maximum message size that is preallocated
  203. Building the Examples
  204. ---------------------
  205. Make sure that you can build the shared library as explained in the previous steps. Even easier way
  206. to build the examples is to install open62541 in your operating system (see :ref:`installing`).
  207. Then the compiler should automatically find the includes and the shared library.
  208. .. code-block:: bash
  209. cp /path-to/examples/tutorial_server_firststeps.c . # copy the example server
  210. gcc -std=c99 -o server tutorial_server_firststeps.c -lopen62541
  211. .. include:: building_arch.rst