openairinterface5g/common/utils/DOC/loader/rtusage.md at develop

mirror of https://gitlab.eurecom.fr/oai/openairinterface5g.git synced 2026-07-13 04:30:28 +00:00

Files

Robert Schmidt 8107939f08 Change OAI license to CSSL v1.0 (and others)

- all RAN code, CI code, configuration files, dockerfiles, in CSSL v1.0
- all deployment code (openshift, charts, ancillary files like shell
  scripts), in MIT
- documentation in CC-BY-4.0
- exceptions might apply and are listed in NOTICE
- there is a new LICENSES folder with all licenses
- CONTRIBUTIONS.md has been updated accordingly

For automated changes based on OAI PL v1.1:

    perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.{c,h,cpp}
    perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.ts
    perl -i~ -0pe 's/<!--.*Licensed to the OpenAirInterface.*openairinterface.org\n.*-->/<!-- SPDX-License-Identifier: LicenseRef-CSSL-1.0 -->/s' **/*.xml

The rest (cmake, files with missing license, cmake) manually.

2026-03-27 16:36:37 +01:00

2.6 KiB

Raw Permalink Blame History

shared library names

Shared library full names are built by the loader using the format:

< path >/lib< module name >< module version >.so

the < module name > is defined at development time, it comes from the modname argument of the load_module_shlib call.
the < module version > and < path > optional parameters, are defined at run-time, depending on the configuration.

loader parameters

The loader is using the configuration module, and defines global and per library parameters. Global parameters must be specified under the loader section and library specific parameters under a loader.<module name> section. Module specific parameters override the global parameters.

Global loader parameters

name	type	default	description
`shlibpath`	`string of char`	`""`	directory path used to look for shared libraries, may be superseded by the library specific `shlibpath`.
`maxshlibs`	`integer`	10	Maximum number of shared libraries the loader can manage.

library specific loader parameters

name	type	default	description
`shlibpath`	`string of char`	`""`	directory path used to look for this shared library.
`shlibversion`	`string of char`	`""`	version to be used to load this shared library.

loader configuration examples

The following configuration file example just reproduce the default loader parameters:

loader :
{
   shlibpath = "./";
   maxshlibs = 10;
   liboai_device :
      {
      shlibpath = "./";
      shlibversion = "";
      }
};

If you want to load a device called liboai_device_USRP.so without writting a specific configuration, you can start the softmodem using the following command:

./lte-softmodem -O libconfig:/usr/local/oai/openairinterface5g/targets/PROJECTS/GENERIC-LTE-EPC/CONF/enb.nbiot.band7.tm1.50PRB.usrpb210.conf:dbgl5 --loader.oai_device.shlibversion _USRP

With this latest example, nn the softmodem logs, you can check that the right device library has been loaded:

[LIBCONFIG] loader.oai_device.shlibpath not found in /usr/local/oai/develop-nb-iot-merge/openairinterface5g/targets/PROJECTS/GENERIC-LTE-EPC/CONF/enb.nbiot.band7.tm1.50PRB.usrpb210.conf
[LIBCONFIG] loader.oai_device.shlibversion set to default value ""
[LIBCONFIG] loader.oai_device: 1/2 parameters successfully set, (1 to default value)
[CONFIG] shlibversion set to  _USRP from command line
[CONFIG] loader.oai_device 1 options set from command line

loader home page

2.6 KiB Raw Permalink Blame History