John Labenski ha scritto:
> On 12/17/06, Francesco Montorsi <[EMAIL PROTECTED]> wrote:
>> Francesco Montorsi ha scritto:
>>> 2) renamed lua5.1 library built by wxLua to libwxlua_gtk2d_lua-2.8.a;
>>> that is, to a lib which follows wxLua naming conventions. This is more
>>> coherent with the way we call the (vanilla) lua intepreter which we
>>> build: wxlua-lua. That is, if we care about not replacing the
>>> system-wide "lua" executable, we should care also about not replacing
>>> the system-wide "lua5.1" library.
>>>
>>> I don't remember why we decided to call our verbatim lua library
>>> "lua5.1"... do you see anything wrong with calling it using our naming
>>> convention?
>> Ok, I now remember why we decided to call it lua5.1; the wx.dll module we
>> build
>> from modules\luamodule is coinceived to be used as any other Lua module.
>> I.e.
>> it must be linked against a DLL/DSO named "lua5.1" not "wxlua_msw28_lua".
>>
>> So, I think we have no other choice that making our "lua" module build a
>> library
>> named lua5.1 and then install it in standard paths, eventually overwriting
>> the
>> preexisting one.
>>
>> This should not be a big problem since the name is versioned and we're using
>> vanilla lua now. It may just be a problem if someone modified lua and thus
>> has
>> in system paths a custom version (but this is a bad practice anyway; that
>> user
>> should consider to name its custom library in some other way).
>>
>> Do you agree with this change?
>
> Can we test in configure if the lua and lua devel packages are
> installed and use those sources? Too much work? I guess it would work
> like wxWidgets use of the jpeg, png, etc libs. I don't know how to do
> any of this. :(
It wouldn't be much difficult from the build-system POV.
The problem may be related to the way we include the lua headers:
#include "lua/include/lua.h"
I'll try to implement the check and then set a wxUSE_CUSTOM_LUA
preprocessor symbol if a usable lua 5.1 is found. The header inclusion
would then be modified:
#if wxUSE_CUSTOM_LUA
#include "lua.h"
#else
#include "lua/include/lua.h"
#endif
otherwise we could also simply add the "modules/lua/include" path to the
paths given to compiler so that we could just use:
#include "lua.h"
all the times.
>> Once we get this up and running I think we should also
>>
>> 1) add our "wx" module to this list:
>>
>> http://lua-users.org/wiki/LuaBinaryModules (look at the end)
>>
>> 2) publish in the next release a single .ZIP download which contains only
>> the
>> wxLua+wxWidgets DLLs + wx.dll module; so that users could just unzip them and
>> start using wx.dll module as for any other lua module.
>
> This would be great, I can compile them with MSVC 6 which I think
> should be the best since it generates the smallest binaries. Can mingw
> use dlls use VC dlls?
yes, absolutely.
Generating them with MSVC6 is probably the best choice also because that
way they probably avoid dependencies on newer MSVC dlls which are
sometimes missing on old systems (I suspect that the DLL I build using
MSVC7.1 requires msvc71.dll or something like that).
Francesco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
