User Tools

Site Tools


doc:lua_make

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
doc:lua_make [2014/02/24 02:10] – [Connect yourself to the central Script Repository] admindoc:lua_make [2014/03/02 07:33] (current) admin
Line 18: Line 18:
 ===== Setup the Cygwin Runtime Environment ===== ===== Setup the Cygwin Runtime Environment =====
  
-To use the much more powerful unix environment instead of just a stupid DOS command interface, you need to install at first a [[http://cygwin.org|CygWin Runtime Environment]]. To do so, please follow the [[cygwininstall|CygWin Installation instructions]]+To use the much more powerful unix environment instead of just a stupid DOS command interface, you need to install at first a [[http://cygwin.org|CygWin Runtime Environment]]. To do so, please follow the [[dev_cygwininstall|CygWin Installation instructions]]
  
 ===== Basics about the Cygwin Environment ===== ===== Basics about the Cygwin Environment =====
Line 77: Line 77:
 The **tools** directory contains all the necessary oobd related programs and scripts. The experienced user might need to know that some of the subdirectories are linked as so called "svn:external" to other repositories. The **tools** directory contains all the necessary oobd related programs and scripts. The experienced user might need to know that some of the subdirectories are linked as so called "svn:external" to other repositories.
  
-The **oobd_groups.pub** is a pgp keyring which contains the public keys of the workgroups, but where the execution rights of the different scripts are controlled.+The **oobd_groups.pub** is a pgp keyring which contains the public keys of the workgroups, by where the execution rights of the different scripts are controlled.
  
 Finally there's the **lua** directory, which contains the lua script files itself and a lot of other stuff: Finally there's the **lua** directory, which contains the lua script files itself and a lot of other stuff:
Line 199: Line 199:
 In opposite to all the complicate setup and explanations above, the build process is just simple: In opposite to all the complicate setup and explanations above, the build process is just simple:
  
-Edit or add the files as you need. For a good start, choose one of the existing *.lua files, copy it to where you need it and give it a clear name. Make sure that the script capapilities do not excedd the security rights of the workgroup folder they are stored in. +Edit or add the files as you need. For a good start, choose one of the existing *.lua files, copy it to where you need it and give it a clear name. Make sure that the script capabilities do not exceed the security rights of the workgroup folder they are stored in. 
  
 Then type in the cygwin command line windows the following commands one after the other. If you do this in a workgroup folder, only the files in that folder will be proceed. If you type the commands in the lua root folder, then all workgroup folders, which you have listed in the local.make will be proccessed. Then type in the cygwin command line windows the following commands one after the other. If you do this in a workgroup folder, only the files in that folder will be proceed. If you type the commands in the lua root folder, then all workgroup folders, which you have listed in the local.make will be proccessed.
Line 205: Line 205:
   - **make clean**: this will remove all older results and temporary files   - **make clean**: this will remove all older results and temporary files
   - **make**: This will convert all module XML files, all other templates and all *.lua files into Lua source files with the extension .luasource. Although normal *.lua files will only been copied by this, this renaming is necessary to not accidently delete some handwritten *.lua files when calling "make clean"   - **make**: This will convert all module XML files, all other templates and all *.lua files into Lua source files with the extension .luasource. Although normal *.lua files will only been copied by this, this renaming is necessary to not accidently delete some handwritten *.lua files when calling "make clean"
-  - **make scripts**: This will now start the real compile process, where the lua- compiler takes all luasource files and translates them into precompiled binaries (+.lbc). Hint: During the compilation of a script all include files are linked together in a temporary file called lua.tmp. If the compiler fails with any error message, that is the right file to look into why the compiler is complaining. +  - **make scripts**: This will now start the real compile process, where the lua- compiler takes all luasource files and translates them into precompiled binaries (*.lbc). Hint: During the compilation of a script all include files are linked together in a temporary file called lua.tmp. If the compiler fails with any error message, that is the right file to look into why the compiler is complaining. 
-  - **make pack**: When enabled and configured in local.make, this call will take all compiled *.lbc files and encrypt them accourding to the workgroup directory in which they are in and copy the result and make up the folderstructure in the target directory, which is also configured in local.make+  - **make pack**: When enabled and configured in local.make, this call will take all compiled *.lbc files and encrypt them accourding to the workgroup directory in which they are inmake up the folderstructure in the target directory, which is also configured in local.make, and and copy the results into it.
      
 After that the final output can be found in the configured target directory, encrypted and ready to distribute. After that the final output can be found in the configured target directory, encrypted and ready to distribute.
doc/lua_make.1393204234.txt.gz · Last modified: 2014/02/24 02:10 by admin