236
236
<dl class="section return"><dt>Returns</dt><dd>The system-specific filename of the module A portable way to build the filename of a module. The platform-specific prefix and suffix are added to the filename, if needed, and the result is added to the directory, using the correct separator character.</dd></dl>
237
237
<p>The directory should specify the directory where the module can be found. It can be <code>0</code> or an empty string to indicate that the module is in a standard platform-specific directory, though this is not recommended since the wrong module may be found.</p>
238
<p>For example, calling g_module_build_path() on a Linux system with a <em>directory</em> of <code>/lib</code> and a <em>module_name</em> of "mylibrary" will return <code>/lib/libmylibrary.so</code>. On a Windows system, using <code>\Windows</code> as the directory it will return <code>\Windows\mylibrary.dll</code>. </p>
238
<p>For example, calling g_module_build_path() on a Linux system with a <em>directory</em> of <code>/lib</code> and a <em>module_name</em> of "mylibrary" will return <code>/lib/libmylibrary.so</code>. On a Windows system, using <code>\\Windows</code> as the directory it will return <code>\\Windows\\mylibrary.dll</code>. </p>
239
239
<dl class="params"><dt>Parameters</dt><dd>
241
241
<tr><td class="paramname">directory</td><td>The directory where the module is. This can be <code>0</code> or the empty string to indicate that the standard platform-specific directories will be used, though that is not recommended. </td></tr>
added
removed
docs/reference/html/classGlib_1_1Module.html
