Commit 17222010 authored by Julien Osman's avatar Julien Osman
Browse files

Merge branch '2238_Document-remote-module' into 'release-8.0'

Document a workaround for a Remote Module bug

See merge request !877
parents 3b6043d5 fc177004
Pipeline #9479 passed with stages
in 90 minutes and 1 second
......@@ -112,13 +112,19 @@ an external CMake project with an existing OTB installation.
* **Building against an installed OTB**
In this case, only the second behaviour (build as standalone) is available. this requires to specify cmake options for the build :
In this case, only the second behaviour (build as standalone) is available. This requires to specify cmake options for the build :
- Set the module to build as standalone with ``OTB_BUILD_MODULE_AS_STANDALONE=ON``
- Set the following option ``-DCMAKE_CXX_FLAGS=-D_GLIBCXX_USE_CXX11_ABI=0`` (see bellow)
- Set the OTB install directory with the variable ``OTB_DIR``
- Set an install folder for your libraries ``CMAKE_INSTALL_PREFIX=/theModulePath/install``
- Set the runtime path *RPATH* of your libraries to your install/lib folder ``DCMAKE_INSTALL_RPATH=/theModulePath/install/lib``
- Tell cmake to set runtime path using link path : ``CMAKE_INSTALL_RPATH_USE_LINK_PATH=TRUE`` (permits to avoid modifying your LD_LIBRARY_PATH)
The OTB binaries are compiled with the option
``GLIBCXX_USE_CXX11_ABI`` set to ``0``. This is why you have to build
your remote module with the same option. If you don't, you will
encounter a "symbol not found" error message while running your
application.
**Compilation and Installation**
......@@ -169,7 +175,6 @@ the applications will be installed in ``/theModuleInstallFolder/lib`` and the bi
We strongly recommend **adding these exports in your .bashrc** in order to make your applications available system wise
Writing your own remote module
------------------------------
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment