Engine:CVAR lib path: Difference between revisions

 
(4 intermediate revisions 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.
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.
  d:\install\engine\lib\namex86.dll
  set lib_path './lib/'
becomes: ./lib/namex86.dll
with install in: d:\install\engine
effective OS load: d:\install\engine\lib\namex86.dll


== Examples ==
== Examples ==
Line 46: Line 49:
=== Formatted names ===
=== Formatted names ===
<pre>
<pre>
namex86.dll
gamex86.dll
namex64.dll
gamex64.dll
namex64.linux.so
gamex64.linux.so
namex64.osx.so
gamex64.osx.so
gamea64.osx.so
</pre>
</pre>


== Notes ==
== Notes ==