I should note that I get a quite a few warnings, but I'm not sure how
to fix or appropriately silence them. They're typically "pointer
truncation from 'void *' to 'long'" or the other way around.
I haven't gone though them all. but for the most part they're for
wxWidgets functions that take or return a void* pointer, but are used
in wxLua to allow Lua programs to store an integer (perhaps an index
into a table with extra data) for convenience.
Regards,
John
On Wed, Apr 2, 2008 at 12:57 AM, John Labenski <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 1, 2008 at 12:13 PM, andre arpin <[EMAIL PROTECTED]> wrote:
> > >
> > > I don't use VC2005, I use VC6, but this doesn't seem right. The wxLua
> > > module is uses DLLs from the other libs. If you want to link against
> > > the other libs (not the DLLs) you should use the monolithic build
> > > which will generate a single wx.dll that only depends on the wxWidgets
> > > DLLs.
> > >
> > > I can try w/ VC2008 tomorrow.
> >
> > I seems to have the same problems with vc2008.
> > It seems to me that if wx.dll was compiled using multilib then only wx.dll
> > would be necessary to use wxlua facilities which would be great. No worry
> > about having dll's out of sync.
>
> The multilib DLL debug compiles and runs ok w/ 2008, aka VC 9, for me.
> I had to rem out the call in the wxlua adv lib for
> wxGridCellWorker::GetRef() however. I added it recently to debug some
> wxGrid problems, however I use a #define hack to add the function
> which works for static libs, but not for DLLs. I will remove it later.
>
> modules/wxbind/src/wxadv_bind.cpp
> int returns = 0; //(self->GetRef());
>
> Additionally, I had to edit msw/setup.h and set this to get the gl dll built.
> #define wxUSE_GLCANVAS 1
>
> ------------------------------
>
> So... in order to get the single wx.dll, I think we need to build
> static libs for everything (wxWidgets and wxLua) and then link the
> wx.dll to them. I suppose that this could work; however we use
> bakefile to generate the build files and I am not sure that you can
> specify that all the other libs are static, but the lib we build is
> dynamic. I can look into it, but I don't have high hopes.
>
> On the other hand, why not just use a staticly built wxLuaFreeze as
> your Lua executable? It is the minimal version of a wxLua program and
> can run any Lua program that lua.exe can. Is there any reason to want
> to dynamically load wx.dll?
>
> Regards,
> John
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
