On Mon, 2008-01-14 at 12:07 -0500, John Labenski wrote:
Yes, if Lua is in your include paths it will try to find it and if
found will use it by default, else specify the path.
$configure --with-lua-prefix=/usr/include/lua5.1
Right, it does indeed fail to detect my system-installed packaged
Hi,
John Labenski ha scritto:
Fixed now, hopefully, please try again.
Sorry, but I don't understand this last change to configure.ac...
I've modified the test and tested it under Ubuntu 7.10 with system's
lua5.1 installed and it seems to work...
The Ubuntu package liblua5.1-0-dev puts
On Jan 15, 2008 6:00 PM, Francesco Montorsi [EMAIL PROTECTED] wrote:
I'm not sure we want to force $lua_prefix/include/lua5.1 because
we're going to find someone with some system who has it elsewhere and
then we'll have more problems.
typically this problem in the configure script I've
Under Debian and Debian-like systems (such as Ubuntu), Lua's header
files are stored in /usr/include/lua5.1/ and the shared object is called
liblua5.1.so. This is so you can have multiple versions installed at
once.
wxLua's configure script does not detect Lua when it is installed in
such a
On 1/14/08, Rob Kendrick [EMAIL PROTECTED] wrote:
Under Debian and Debian-like systems (such as Ubuntu), Lua's header
files are stored in /usr/include/lua5.1/ and the shared object is called
liblua5.1.so. This is so you can have multiple versions installed at
once.
wxLua's configure script
John Labenski ha scritto:
On 1/14/08, Rob Kendrick [EMAIL PROTECTED] wrote:
Under Debian and Debian-like systems (such as Ubuntu), Lua's header
files are stored in /usr/include/lua5.1/ and the shared object is called
liblua5.1.so. This is so you can have multiple versions installed at
once.
On 1/14/08, Rob Kendrick [EMAIL PROTECTED] wrote:
On Mon, 2008-01-14 at 10:52 -0500, John Labenski wrote:
Francesco, I think this should fix it. Add new
--enable-systemlua=yes/no/auto.
snip
Forgive my ignorance of issues relating to the creation of configure
scripts, but does this
On Mon, 2008-01-14 at 10:52 -0500, John Labenski wrote:
Francesco, I think this should fix it. Add new --enable-systemlua=yes/no/auto.
snip
Forgive my ignorance of issues relating to the creation of configure
scripts, but does this also solve the issue of it not finding where Lua
is installed
