Llewellyn/conky
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/conky.git synced 2024-11-18 02:55:12 +00:00
Code Issues Releases Activity
000f0779aa
conky/3rdparty/toluapp/INSTALL

43 lines
1.7 KiB
Plaintext
Raw Normal View History

Add toluapp subtree (#712) * First commit! * Import to git * Droping down CMake requirement * Corrected installation of libraries * Adding travis build * Updated cmake macros * Fixed find package * Updated travis hook * Updated travis hook * Patch to support Lua 5.3. * Fix Lua header include directives in tolua++.h Use angle bracket rather than double quotes when including Lua headers in the tolua++ header. This fixes a problem on systems that default to a Lua version newer than 5.1 and install the tolua++ header to the same directory as newer Lua headers. As there are (usually) no Lua headers in the same directory when building tolua++ itself, the preprocessor will look to the include directories passed to the compiler, one of which would be the Lua 5.1 include directory, and tolua++ will build with those (correct) headers. Then the tolua++ header is usually installed in the default include directory, alongside the newer Lua headers, which you wouldn't expect to cause any trouble. But it does cause trouble when trying to build other programs that include the tolua++ header, because now the preprocessor does find Lua headers in the same directory as the tolua++ header, which are the newer (incorrect) headers. Now the program will either fail to compile, because it doesn't support the newer headers, or fail to link with the tolua++ shared object because they were compiled against different Lua headers. Using angle brackets instead of double quotes in the include directives will fix the problem, because then the preprocessor will look to the include directories passed to the compiler first. See http://www.cegui.org.uk/forum/viewtopic.php?f=10&t=7195 * Remove email notifications. * Update travis build. * Build shared and static libs. * Patch toluapp to support Lua 5.3. With this change, support for Lua 5.1 is dropped. This resolve #116. * Add some comments to clarify the toluapp handling. * Add minor sonar fix.
2018-12-20 20:18:51 +00:00
This version of tolua++ uses SCons to compile (http://www.scons.org). SCons uses
pythin. If you don't want to install python, check "Installation without scons"
below.
* Installation
1. Edit the "config" file for your platform to suit your environment,
if at all necessary (for cygwin, mingw, BSD and mac OSX use
'config_posix')
2. Then, type "scons".
You can use 'scons -h' to see a list of available command line options.
* What you get
If "scons" succeeds, you get:
* an executable to generate binding code in ./bin;
* the C library to be linked in your application in ./lib;
* the include file needed to compile your application in ./include.
These are the only directories you need for development, besides Lua.
You can use 'scons install' to install the files, see the 'prefix' option.
* Installation without scons
The instructions for building tolua++ without scons depend on the particular
compiler you are using.
The simplest way is to create a folder with all .c and .h files except
'toluabind_default.c', and then create a project for the executable and the
library, as follows:
tolua.exe: all *.c *.h in src/bin (except toluabind_default.c)
tolua.lib: all *.c *.h in src/lib.
* Installation with Microsoft Visual Studio
The directory 'win32' contains project files for Microsoft Visual Studio 7
(contributed by Makoto Hamanaka). The project has 4 different build options:
withLua50_Release, withLua51_Release, withLua50_Debug and withLua51_Debug.
They all expect the lua library names used by the LuaBinaries packages
(http://luabinaries.luaforge.net/). The resulting files are built on /lib and
/bin (for the library and tolua++.exe).
Copy Permalink