[Wxlua-users] Re: wxLua shared build status

[Francesco M. <f18...@ya...>]

John Labenski ha scritto:
> On 5/20/06, Francesco Montorsi 
> <f18...@ya...> wrote:
>> Hi,
>>    I did various changes and now using SHARED=1 option wxLua compiles
>> smoothly as a dll also on windows.
>>
>> Nonetheless, there are two problems:
>>
>> 1) the wx.dll which is created by MSVC, generates the following error
>> when used through luamodule.wx.lua sample:
>>
>> "Cannot find a required procedure"
>>
>> (the message is localized so I'm translating it)... maybe that's because
>> wx.dll is a dll which in reality does not contain any code apart from
>> wxLua\modules\luamodule\src\luamodule.cpp (it's just 34K IIRC) ?
>> Nonetheless it should force lua to import all other DLLs from which it
>> depends (wxlua* and wx* ones)...
> 
> Sounds like you got this fixed in your next message. :)
yes, exactly ;)

> 
>> Unfortunately I've upgraded to latest Mingw which gives an internal
>> error when compiling wx_bind.cpp and
> 
> Where, what? There are a lot of #if statements, maybe too many for it?
it was an internal gcc bug 
(https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1492239&group_id=2435) 
which I've been told has been fixed in gcc 4; I'll try with it asap.


> 
>> borland is giving me strange errors
>> about wxLUA_DECLARE_ENCAPSULATION so I can't verify if this happens also
>> with other win32 compilers...
> 
> Anything that can be fixed?
I didn't dig too deep but I'll do.

> Borland is pretty antique isn't it? 
the free version yes; but it's still the fastest compiler ever created 
and it also produces very fast executables :)

>IIRC
> you cannot build a lib since it overflows trying to build wxWidgets
> itself.
there is an excess of debug info when using BUILD=debug SHARED=0, but 
since I mainly use it only for release builds this has never been a big 
problem for me

> I guess it's only usable for DLLs.
or for static release libraries - BTW I think that next wxLua binary 
releases for win32 should use DLLs (so that one can just redistribute 
the *dll files without even have to recompile wxLua statically in its 
project)...

> 
>> 2) setting the #define wxLuaDebugServer to 1 in wxluasetup.h generates a
>> dependency of wxbind module to the wxluasocket (and thus also to
>> wxluadebug) module. Is this a good thing to do ?
>> Shouldn't we keep all wxLuaDebugServer stuff in the wxluasocket module?
> 
> Yes. This is a throwback to when we had a single monolithic binding. I
> can change this so that the wxLuaSocket stuff will go into
> modules/wxluasocket. This means that there will be another binding dir
> wxluasocket and it will output into the wxluasocket module src dir to
> get compiled along with the current wxluasocket code.
I think this should be done...

Francesco