Engine:CVAR lib path - Revision history

Bear: /* Details */

2023-10-16T19:52:53Z

Details

← Older revision		Revision as of 19:52, 16 October 2023
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 ~~concantinated~~ verbatim to the ~~calcualted~~ library file name to create the final library load path.		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

2023-10-16T19:51:30Z

Details

← Older revision		Revision as of 19:51, 16 October 2023
Line 33:		Line 33:
	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

2023-10-16T19:51:09Z

← Older revision		Revision as of 19:51, 16 October 2023
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 concantinated verbatim to the calcualted library file name to create the final library load path.
	d:\install\engine\lib\namex86.dll		set lib_path './lib/'
			becomes: ./lib/namex86.dll
			install: d:\install\engine
			effective OS load: d:\install\engine\lib\namex86.dll

	== Examples ==		== Examples ==

2023-10-16T19:45:50Z

Formatted names

2023-10-16T19:45:30Z

Formatted names

2023-10-16T19:44:59Z

Details

← Older revision		Revision as of 19:44, 16 October 2023
Line 16:		Line 16:

	[name][platform][.os][.extension]		[name][platform][.os][.extension]
			namex86.dll

	Platform names:		Platform names:
Line 30:		Line 31:

	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.
			d:\install\engine\lib\namex86.dll

	== Examples ==		== Examples ==

2023-10-16T19:41:03Z

← Older revision		Revision as of 19:41, 16 October 2023
Line 27:		Line 27:
	* .osx - Mac OS, 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 ~~luanch~~ 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.

	== Examples ==		== Examples ==

2023-10-16T19:34:22Z

← Older revision		Revision as of 19:34, 16 October 2023
Line 29:		Line 29:
	The path is either a full OS file system path to the library location, or a path relative to the luanch 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 luanch location, which is the location of the executable for the engine.

	~~So for~~ the path executable path 'd:\install\engine.exe', and a 'lib_path' of './lib/':		== Examples ==
			=== Default values ===
			For the path executable path 'd:\install\engine.exe', and a 'lib_path' of './lib/':
	\install		\install
	engine.exe		engine.exe
Line 38:		Line 40:
	...		...

	~~== Examples ==~~
	=== Formatted names ===		=== Formatted names ===
	<pre>		<pre>

2023-10-16T19:32:49Z

Details

← Older revision		Revision as of 19:32, 16 October 2023
Line 29:		Line 29:
	The path is either a full OS file system path to the library location, or a path relative to the luanch 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 luanch location, which is the location of the executable for the engine.

	So, for an path executable path 'd:\install\engine.exe' and 'lib_path' of './lib/':		So for the path executable path 'd:\install\engine.exe', and a 'lib_path' of './lib/':
	\install		\install
	engine.exe		engine.exe

2023-10-16T19:32:20Z

Details

@@ Line 26: / Line 26: @@
 * .linux - Linux, using the '.so' extension
 * .osx - Mac OS, using the '.so' extension
 == Examples ==