FAQ¶

• FAQ
  • [C++, Python] I compiled and installed successfully, but communication does not work
  • [C++] I compiled and installed successfully, but RSB binaries/libraries produce linker errors at runtime

[C++, Python] I compiled and installed successfully, but communication does not work¶

Starting with version 0.5, RSB uses a transport that implements communication within a single process by default. In other words, network communcation is disbabled by default.

This can be changed in three ways:

1. Globally for all RSB programs running under the UNIX user
   Create or modify a RSB configuration file ~/.config/rsb.conf to contain the following lines:
   

   [transport.spread]
   enabled = 1
   [transport.inprocess]
   enabled = 0
   

   
   Lines 3 and 4 can be omitted to enable both transports in parallel.
2. Locally for the current directory
   Create a RSB configuration file $(pwd)/rsb.conf with the same contents as described above.
3. For the current shell
   Set and export environment variables as follows
   

   $ export RSB_TRANSPORT_SPREAD_ENABLED=1
   $ export RSB_TRANSPORT_INPROCESS_ENABLED=1
   

[C++] I compiled and installed successfully, but RSB binaries/libraries produce linker errors at runtime¶

The C++ implementation of RSB is built without fixed rpath by default. As a result, installed RSB binaries and libraries do not contain information regarding the location of their dependencies. This potentially causes runtime linking to fail because the dependencies cannot be located.

There two possible solutions:

1. Build and installing RSB with fixed rpath
   This can be achieved by configuring RSB with
   

     cmake -D?=?
     

2. Use of the LD_LIBRARY_PATH variable
   TODO