dany/luasocket
1
0
Fork 0
mirror of https://github.com/lunarmodules/luasocket.git synced 2024-07-05 20:59:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

Changed LIB/SHARE to CDIR/LDIR.

Browse Source
This commit is contained in:
Diego Nehab 2005-11-22 20:51:28 +00:00
parent d55a5826e8
commit 7dace4af7e
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
doc/installation.html
View File

@ -65,26 +65,26 @@ the package scheme will likely already have been answered.
<p> On Unix systems, the standard distribution uses two base <p> On Unix systems, the standard distribution uses two base
directories, one for system dependent files, and another for system directories, one for system dependent files, and another for system
independent files. Let's call these directories <tt>&lt;LIB&gt;</tt> independent files. Let's call these directories <tt>&lt;CDIR&gt;</tt>
and <tt>&lt;SHARE&gt;</tt>, respectively. and <tt>&lt;LDIR&gt;</tt>, respectively.
For instance, in my laptop, I use '<tt>/usr/local/lib/lua/5.0</tt>' for For instance, in my laptop, I use '<tt>/usr/local/lib/lua/5.0</tt>' for
<tt>&lt;LIB&gt;</tt> and '<tt>/usr/local/share/lua/5.0</tt>' for <tt>&lt;CDIR&gt;</tt> and '<tt>/usr/local/share/lua/5.0</tt>' for
<tt>&lt;SHARE&gt;</tt>. On Windows, sometimes only one directory is used, say <tt>&lt;LDIR&gt;</tt>. On Windows, sometimes only one directory is used, say
'<tt>c:\program files\lua\5.0</tt>'. Here is the standard LuaSocket '<tt>c:\program files\lua\5.0</tt>'. Here is the standard LuaSocket
distribution directory structure:</p> distribution directory structure:</p>
<pre class=example> <pre class=example>
&lt;SHARE&gt;/compat-5.1.lua &lt;LDIR&gt;/compat-5.1.lua
&lt;SHARE&gt;/ltn12.lua &lt;LDIR&gt;/ltn12.lua
&lt;SHARE&gt;/socket.lua &lt;LDIR&gt;/socket.lua
&lt;LIB&gt;/socket/core.dll &lt;CDIR&gt;/socket/core.dll
&lt;SHARE&gt;/socket/http.lua &lt;LDIR&gt;/socket/http.lua
&lt;SHARE&gt;/socket/tp.lua &lt;LDIR&gt;/socket/tp.lua
&lt;SHARE&gt;/socket/ftp.lua &lt;LDIR&gt;/socket/ftp.lua
&lt;SHARE&gt;/socket/smtp.lua &lt;LDIR&gt;/socket/smtp.lua
&lt;SHARE&gt;/socket/url.lua &lt;LDIR&gt;/socket/url.lua
&lt;SHARE&gt;/mime.lua &lt;LDIR&gt;/mime.lua
&lt;LIB&gt;/mime/core.dll &lt;CDIR&gt;/mime/core.dll
</pre> </pre>
<p> Naturally, on Unix systems, <tt>core.dll</tt> <p> Naturally, on Unix systems, <tt>core.dll</tt>
@ -96,7 +96,7 @@ environment variables need to be set. The first environment variable tells
the interpreter to load the <tt>compat-5.1.lua</tt> module at startup: </p> the interpreter to load the <tt>compat-5.1.lua</tt> module at startup: </p>
<pre class=example> <pre class=example>
LUA_INIT=@&lt;SHARE&gt;/compat-5.1.lua LUA_INIT=@&lt;LDIR&gt;/compat-5.1.lua
</pre> </pre>
<p> <p>
@ -106,8 +106,8 @@ directories and with the appropriate filename extensions.
</p> </p>
<pre class=example> <pre class=example>
LUA_PATH=&lt;SHARE&gt;/?.lua;?.lua LUA_PATH=&lt;LDIR&gt;/?.lua;?.lua
LUA_CPATH=&lt;LIB&gt;/?.dll;?.dll LUA_CPATH=&lt;CDIR&gt;/?.dll;?.dll
</pre> </pre>
<p> Again, naturally, on Unix systems the shared library extension would be <p> Again, naturally, on Unix systems the shared library extension would be