diff options
Diffstat (limited to 'html')
| -rw-r--r-- | html/download/.cvsignore | 3 | ||||
| -rw-r--r-- | html/en/building.html | 183 |
2 files changed, 130 insertions, 56 deletions
diff --git a/html/download/.cvsignore b/html/download/.cvsignore index 7e9ea7e..a47299f 100644 --- a/html/download/.cvsignore +++ b/html/download/.cvsignore @@ -2,3 +2,6 @@ cd.chm cd.pdf gdiplus.* PDFlib-Lite-license.pdf +install_dev +install +config_lua_module
\ No newline at end of file diff --git a/html/en/building.html b/html/en/building.html index 32b6691..737cf1c 100644 --- a/html/en/building.html +++ b/html/en/building.html @@ -11,10 +11,12 @@ <h1 align="center" style="text-align:center">Building Lua, IM, CD and IUP in Linux</h1> <p>This is a guide to build all the Lua, IM, CD and IUP libraries in Linux. -Notice that you may not use all the libraries, but this guide will build all of -them. Later on it is explained how to build a single library.</p> +Notice that you may not use all the libraries, although this guide will show you +how to build all of +them. You may then choose to build specific libraries.</p> +<p>The Linux used as reference is the Ubuntu distribution.</p> <h3>System Configuration</h3> -<p>You will have to download the development version of some packages installed +<p>To build the libraries you will have to download the development version of some packages installed on your system. Although the run time version of some of these packages are already installed, the development versions are usually not. The packages described here are for Ubuntu, but you will be able to identify them for other @@ -24,7 +26,8 @@ systems as well.</p> <p>To build IM you will need:</p> <pre>g++</pre> <p>To build CD you will need:</p> -<pre>libx11-dev +<pre>libfreetype6-dev +libx11-dev libxpm-dev libxmu-dev libxft-dev (for the XRender driver, OPTIONAL) @@ -34,9 +37,12 @@ libgtk2.0-dev (for the GDK driver)</pre> <pre>libgtk2.0-dev (for the GTK driver) [already installed for CD] libmotif-dev and x11proto-print-dev (for the Motif driver, OPTIONAL) libgl1-mesa-dev and libglu1-mesa-dev (for the IupGLCanvas)</pre> -<h3>Download</h3> +<p>To install them you can use the Synaptic Package Manager and select the +packages, or can use the command line and type:</p> +<pre>sudo apt-get install package_name</pre> +<h3>Source Download</h3> <p>Download the "xxx-X.X_Sources.tar.gz" package from the "<strong>Docs and Sources</strong>" -folder for the version you want to build. Here are links for the <strong>Files</strong> section +directory for the version you want to build. Here are links for the <strong>Files</strong> section in <strong>Source Forge</strong>:</p> <p>Lua - <a href="http://sourceforge.net/projects/luabinaries/files/"> http://sourceforge.net/projects/luabinaries/files/</a><br> @@ -46,73 +52,138 @@ CD - <a href="http://sourceforge.net/projects/canvasdraw/files/"> http://sourceforge.net/projects/canvasdraw/files/</a><br> IUP - <a href="http://sourceforge.net/projects/iup/files/"> http://sourceforge.net/projects/iup/files/</a></p> -<h3>Lua</h3> -<p>Although we use Lua from LuaBinaries, any Lua installation can also be used. -But you will have to define some environment variables before building IM, CD and -IUP. Here is an example:</p> -<pre class="example">export LUA_SUFFIX= -export LUA_INC=/usr/local/include [actually NOT necessary, this one is already used by gcc/g++] -export LUA_LIB=/usr/local/lib [ " ] -export LUA_BIN=/usr/local/bin [necessary because luac will not be used from the PATH]</pre> -<p>The tools <strong>bin2c</strong> and <strong>luac</strong> are necessary only if you need to rebuild LOH files. -But since the source packages already includes them, those tools are in fact not -necessary.</p> <h3>Unpacking</h3> +<p>To extract the files use the tar command at a common directory, for example:</p> +<pre>mkdir -p xxxx +cd xxxx + +[copy the downloaded files, to the xxxx directory] + +tar -xpvzf iup-3.2_Sources.tar.gz +tar -xpvzf cd-5.4_Sources.tar.gz +tar -xpvzf im-3.6.2_Sources.tar.gz +tar -xpvzf lua5_1_4_Sources.tar.gz [optional, see note bellow]</pre> <p>If you are going to build all the libraries, the makefiles and projects expect the following directory tree:</p> <pre>/xxxx/ - iup/ cd/ im/ - lua5.1/ [optional]</pre> + iup/ + lua5.1/ [optional, see note bellow]</pre> -<p>So, unpack all the source packages in the same folder that will do fine.</p> +<p>If you unpack all the source packages in the same directory, that structure will +be automatically created.</p> +<h3>Lua</h3> +<p>Although we use Lua from LuaBinaries, any Lua installation can also be used. +In Ubuntu, the Lua run time package is:</p> +<pre>lua5.1</pre> +<p>And the Lua development package is:</p> +<pre>liblua5.1-0-dev</pre> +<p>To use them, instead of using the directory "/xxxx/lua5.1" described above, you will have to define some environment variables before building IM, CD and +IUP:</p> +<pre class="example">export LUA_SUFFIX= +export LUA_INC=/usr/include/lua5.1</pre> <h3>Building</h3> <p>As a general rule (excluding system dependencies): IUP depends on CD and IM, and CD depends on IM. So start by build IM, then CD, then IUP.</p> -<p>To start building go the the "<strong>src</strong>" folder and type "<strong>make</strong>". In IUP there are -many "srcxxx" folders, so go to the up folder "iup" and type +<p>To start building go the the "<strong>src</strong>" directory and type "<strong>make</strong>". In IUP there are +many "srcxxx" folders, so go to the up directory "iup" and type "<strong>make</strong>" that all the -sub folders will be built.</p> -<p>Instead of building all the libraries, try building only the libraries you +sub folders will be built. For example:</p> +<pre>cd im/src +make +cd ../.. + +cd cd/src +make +cd ../.. + +cd iup +make +cd ..</pre> +<p><strong>TIP</strong>: Instead of building all the libraries, try building only the libraries you are going to use. The provided makefiles will build all the libraries, but take a look inside them and you will figure out how to build just one library. </p> -<h3>Installation</h3> - -<p>After building you can copy the libraries files to the system folder. This is -not necessary since you can use -I and -L on your makefiles, but it can be done. -If you are inside one of the libraries main folder you can type:</p> -<pre>cp lib/Linux26g4/* /usr/local/lib -cp include/* /usr/local/include</pre> -<p>This will copy run time and development files. If you just want the run time, -then do simply:</p> -<pre>cp lib/Linux26g4/*.so /usr/local/lib</pre> -<p>Also when coping development folders, if you want to keep the library headers -in a separate folder, you can do:</p> -<pre>cp -R iup/include /usr/local/include/iup -cp -R cd/include /usr/local/include/cd -cp -R im/include /usr/local/include/im</pre> -<p>Then use in your makefile -Iiup -Icd -Iim.</p> -<p>This installation procedure also can be used for the pre-compiled binaries -packages available for download. They contain the development and run time files -you need. </p> -<p>If you <strong>don't</strong> want to copy the libraries to your system -folder, you can still use them, but you will need to add the binaries folders to +<h3>Pre-compiled Binaries</h3> +<p>Instead of building from sources you can try to use the pre-compiled +binaries. Usually they were build in the latest Ubuntu versions for 32 and 64 +bits. The packages are located in the "<strong>Linux Libraries</strong>" +directory +under the <strong>Files</strong> section +in <strong>Source Forge</strong>, with <strong>"xxx-X.X_Linux26g4_lib</strong>.<strong>tar.gz"</strong> +and <strong>"xxx-X.X_Linux26g4_64_lib.tar.gz"</strong> names.</p> +<p>Do not extract different pre-compiled binaries in the same directory, create a +subdirectory for each one, for example:</p> +<pre>mkdir iup +cd iup +tar -xpvzf ../iup-3.2_Linux26g4_lib.tar.gz +cd .. + +mkdir cd +cd cd +tar -xpvzf cd-5.4_Linux26g4_lib.tar.gz +cd .. + +mkdir im +cd im +tar -xpvzf im-3.6.2_Linux26g4_lib.tar.gz +cd .. + +</pre> +<p>For the installation instructions bellow, remove the "lib/Linux26g4" from the +following examples if you are using the pre-compiled binaries.</p> +<h3>Installation (System Directory)</h3> + +<p>After building you can copy the libraries files to the system directory. If you are inside +the main directory, to install the run time libraries you can type, for example:</p> +<pre>sudo cp -f iup/lib/Linux26g4/*.so /usr/lib [script version: <a href="../download/install">install</a> ] +sudo cp -f cd/lib/Linux26g4/*.so /usr/lib +sudo cp -f im/lib/Linux26g4/*.so /usr/lib</pre> +<p>To install the development files, +then do:</p> +<pre>sudo mkdir -p /usr/include/iup [script version: <a href="../download/install_dev">install_dev</a> ] +sudo cp -f iup/include/*.h /usr/include/iup +sudo cp -f iup/lib/Linux26g4/*.a /usr/lib + +sudo mkdir -p /usr/include/cd +sudo cp -f cd/include/*.h /usr/include/cd +sudo cp -f cd/lib/Linux26g4/*.a /usr/lib + +sudo mkdir -p /usr/include/im +sudo cp -fR im/include/*.h /usr/include/im +sudo cp -f im/lib/Linux26g4/*.a /usr/lib</pre> +<p>Then in your makefile use -Iiup -Icd -Iim for includes. There is no need to +specify the libraries directory with -L. Development files are only necessary if +you are going to compile an application or library in C/C++ that uses there +libraries. To just run Lua scripts they are not necessary.</p> +<h4>Installation (Build Directory) [Alternative]</h4> +<p>If you <strong>don't</strong> want to copy the run time libraries to your system +directory, you can use them from build directory. You will need to add the run time +libraries folders to the LD_LIBRARY_PATH, for example:</p> <pre>export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/xxxx/iup/lib/Linux26g4:/xxxx/cd/lib/Linux26g4:/xxxx/im/lib/Linux26g4</pre> -<p>In this case, in your makefile will will also need to specify those paths -when linking using -L/xxxx/iup/lib/Linux26g4.</p> -<h4>Lua</h4> -<p>If you are NOT using LuaBinaries then you have two options to be able to use -"require" with these libraries. You can create symbolic links in the Lua C -modules folder to the installed libraries run time:</p> -<pre>ln -s /usr/local/lib/lipiuplua51.so /usr/local/lib/lua/5.1/iuplua.so -ln -s /usr/local/lib/lipiupluacontrols51.so /usr/local/lib/lua/5.1/iupluacontrols.so +<p>And in your makefile will will also need to specify those paths +when linking using -L/xxxx/iup/lib/Linux26g4, and for compiling use +-I/xxxx/iup/include.</p> +<h3>Installation (Lua Modules)</h3> +<p>Lua modules in Ubuntu are installed in the "/usr/lib/lua/5.1" +directory. So to +be able to use the Lua "require" with IUP, CD and IM you must create symbolic links inside +that directory.</p> +<pre>sudo mkdir -p /usr/lib/lua/5.1 [script version: <a href="../download/config_lua_module">config_lua_module</a> ] +cd /usr/lib/lua/5.1 + +sudo ln -fs /usr/lib/libiuplua51.so iuplua.so +sudo ln -fs /usr/lib/libiupluacontrols51.so iupluacontrols.so ...</pre> -<p>You can set the LUA_CPATH environment variable:</p> -<pre>export LUA_CPATH=./\?.so\;./lib\?.so\;./lib\?51.so\; -</pre> +<p>Using those links you do not need any extra configuration. </p> +<h4>Installation (Lua Modules) [Alternative]</h4> +<p>If you use the <strong>alternative</strong> installation directory, and you also +do NOT use the LuaBinaries installation, then you must set the LUA_CPATH environment variable:</p> +<pre>export LUA_CPATH=./\?.so\;./lib\?.so\;./lib\?51.so\;</pre> +<p><br> +</p> </body> |