Engine:CVAR lib path: Difference between revisions
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 30: | Line 30: | ||
The path is either a full OS file system path to the library location, or a path relative to the launch location, which is the location of the executable for the engine. | The path is either a full OS file system path to the library location, or a path relative to the launch location, which is the location of the executable for the engine. | ||
In some configurations the path is relative to the current directory and not necessarily the actual engine start location. The 'lib_path' will be | In some configurations the path is relative to the current directory and not necessarily the actual engine start location. The 'lib_path' will be concatenated verbatim to the calculated library file name to create the final library load path. | ||
set lib_path './lib/' | set lib_path './lib/' | ||
becomes: ./lib/namex86.dll | becomes: ./lib/namex86.dll | ||
install: d:\install\engine | with install in: d:\install\engine | ||
effective OS load: d:\install\engine\lib\namex86.dll | effective OS load: d:\install\engine\lib\namex86.dll | ||
Latest revision as of 19:52, 16 October 2023
Path for loading native 'world' libraries.
set lib_path './lib/'
Arguments[edit]
- name - 'lib_path'
- value - Full or start folder relative path that contains loadable native world libraries. Default value is './lib/'.
Associations[edit]
- Is by default placed in the 'global' context.
Details[edit]
Path to the platform native libraries for the world.
The library file name format uses name suffixes to distinguish between versions of the same library compiled for different platforms. Modules will load by finding the correct one by name, platform, OS, and OS module type extension.
[name][platform][.os][.extension] namex86.dll
Platform names:
- x86 - 32-bit x86 platform
- x64 - 64-bit x64 platform
- a64 - 64-bit ARM platform
OS names:
- (none) - Windows, using the '.dll' extension
- .linux - Linux, using the '.so' extension
- .osx - Mac OS, using the '.so' extension
The path is either a full OS file system path to the library location, or a path relative to the launch location, which is the location of the executable for the engine.
In some configurations the path is relative to the current directory and not necessarily the actual engine start location. The 'lib_path' will be concatenated verbatim to the calculated library file name to create the final library load path.
set lib_path './lib/' becomes: ./lib/namex86.dll with install in: d:\install\engine effective OS load: d:\install\engine\lib\namex86.dll
Examples[edit]
Default values[edit]
For the path executable path 'd:\install\engine.exe', and a 'lib_path' of './lib/':
\install
engine.exe
lib
gamex86.dll
gamex64.dll
data
...
Formatted names[edit]
gamex86.dll
gamex64.dll
gamex64.linux.so
gamex64.osx.so
gamea64.osx.so