wxlua-users Mailing List for wxLua (Page 3)

John Labenski <jlabenski@...> writes:
> 
> On 8/1/07, Andre <arpin@...> wrote:
> > John Labenski <jlabenski <at> ...> writes:
> > > Ok, that's the current CVS. Hopefully you'll get the same results with 
that.
I do not, I am sorry but something is wrong
I re-install version 6 of the compiler
I got a fresh version of wxlua one hour ago (deleted the old one first)
re-install wxwidget from the zip file for version 2.8 and made no changes
nmake -f makefile.vc USE_OPENGL=1 (using version 6)
wxwidget, stc, wxlua and run my program it fail
copy your executable and it works
is cvs right?
Andre

On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
> On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
> > On 8/1/07, John Labenski <jla...@gm...> wrote:
> >
> > > Humm, I do not think you have the current CVS. Please compare your
> > > apps/build/msw/makefile.gcc. Do you have the variable
> > > $(__WXLIB_GL_NAME_p)?
> >
>
> I just downloaded the 7-1-2007 nightly source and it doesn't have that
> variable in any of the make files located in 'wxLua\build\msw'. That is
> where I am building from. Is that not the right place? I got my instructions
> from the website (
> http://wxlua.sourceforge.net/docs/install.html) under 2.
> Building on Windows using makefiles.
Yes you can use the one in wxLua/build/msw since it just calls make
for the makefiles for the modules and apps.
> It does have that variable in the 07-31-2007 when I look at the makefile in
> 'apps/build/msw/makefile.gcc'.
Good, I assume it works correctly now.
-John Labenski

On 8/1/07, John Labenski <jla...@gm...> wrote:
>
> Humm, I do not think you have the current CVS. Please compare your
> apps/build/msw/makefile.gcc. Do you have the variable
> $(__WXLIB_GL_NAME_p)?
You are correct it is not in the makefile. I am sorry but I can't access CVS
from work (also another reason I suggested svn ;-) ) and I downloaded
nightly archive. I will download the one the came out last night and try
again.
-- 
Regards,
Ryan
RJP Computing

On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
>
> On 8/1/07, John Labenski <jla...@gm...> wrote:
> >
> > Humm, I do not think you have the current CVS. Please compare your
> > apps/build/msw/makefile.gcc. Do you have the variable
> > $(__WXLIB_GL_NAME_p)?
>
>
I just downloaded the 7-1-2007 nightly source and it doesn't have that
variable in any of the make files located in 'wxLua\build\msw'. That is
where I am building from. Is that not the right place? I got my instructions
from the website (http://wxlua.sourceforge.net/docs/install.html) under 2.
Building on Windows using makefiles.
It does have that variable in the 07-31-2007 when I look at the makefile in
'apps/build/msw/makefile.gcc'.
-- 
Regards,
Ryan
RJP Computing

John Labenski <jlabenski@...> writes:
> 
> On 8/1/07, Andre <arpin@...> wrote:
> > John Labenski <jlabenski <at> ...> writes:
> >
> I think you need to edit wxWidgets/include/wx/msw/setup.h and set
> wxUSE_OPENGL 1.
> 
> Either that or just remove the lib in the build file.
> 
> Unfortunately there's no easy way to allow people to pick and choose
> the libs to link to. The code can use #if statements, but there's
> nothing equivalent for the linker command.
> 
I did this and I still have the same problem.
I have deleted wxlua and got a fresh copy from an then made it.
I will now delete wxwidgets and get a fresh copy 
and use version 6 of the compiler if I can.
This will take a while.
Andre

On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
> On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
> >
> >
> > I think there is a problem because I can't complie it either with mingw
> and I have built the GL (wxmsw28ud_gl.a) libraries.
> >
>
> Here is the command line that is produced. Notice that linking to the GL
> library is missing.
>
> g++ -o ..\..\..\bin\gcc_lib\wxlua.exe gccmsw\app_wxlua_lconsole.o
> gccmsw\app_wxlua_wxlua.o gccmsw\app_wxlua_wxlua_rc.o
> -mthreads -LD:\devel\Libraries\wxWidgets2.8\lib\gcc_lib
> -L..\..\..\lib\gcc_lib -L..\..\..\modules\lua\lib -Wl,--subsys
> tem,windows -mwindows -lwxlua_msw28_wxluasocket -lwxlua_msw28_wxluadebug
> -lwxlua_msw28_wxbindadv -lwxlua_msw28_wxbinda
> ui -lwxlua_msw28_wxbindbase -lwxlua_msw28_wxbindcore -lwxlua_msw28_wxbindgl
> -lwxlua_msw28_wxbindhtml -lwxlua_msw28_wxbin
> dmedia -lwxlua_msw28_wxbindnet -lwxlua_msw28_wxbindstc
> -lwxlua_msw28_wxbindxml -lwxlua_msw28_wxbindxrc -lwxlua_msw28_wxl
> ua -llua5.1 -lwxmsw28_stc -lwxmsw28_xrc -lwxmsw28_html -lwxmsw28_aui
> -lwxmsw28_media -lwxmsw28_adv -lwxbase28_net -lwxba
> se28_xml -lwxmsw28_core -lwxbase28 -lwxtiff -lwxjpeg -lwxpng -lwxzlib
> -lwxregex -lwxexpat -lkernel32 -luser32 -lgdi32 -l
> comdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid
> -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32
> --
Humm, I do not think you have the current CVS. Please compare your
apps/build/msw/makefile.gcc. Do you have the variable
$(__WXLIB_GL_NAME_p)?
..\..\..\bin\gcc_$(____app_23)\wxlua.exe: make_dir_app_wxlua
$(APP_WXLUA_OBJECTS)
gccmsw$(WXLIBPOSTFIX)$(_BUILDDIR_SHARED_SUFFIX)\app_wxlua_w
xlua_rc.o
 $(CXX) -o $@ $(APP_WXLUA_OBJECTS) $(LDFLAGS) -mthreads
-L$(WX_DIR)$(WXLIBPATH) $(____app_21) $(__THREADING)
-L..\..\..\lib\gcc_$(____a
pp_17) -L$(LUA_DIR)\lib -Wl,--subsystem,windows -mwindows
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxluasocket
-lwxlua_msw$(WX_VERSION)$(WXLI
BPOSTFIX)_wxluadebug -lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindadv
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindaui
-lwxlua_msw$(WX_VERSI
ON)$(WXLIBPOSTFIX)_wxbindbase
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindcore
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindgl -lwxlua_msw$
(WX_VERSION)$(WXLIBPOSTFIX)_wxbindhtml
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindmedia
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindnet -
lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindstc
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxbindxml
-lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxb
indxrc -lwxlua_msw$(WX_VERSION)$(WXLIBPOSTFIX)_wxlua -llua5.1
-lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_stc $(__WXLIB_XRC_NAME_p)
$(__WXLIB_HTML_NAM
E_p) $(__WXLIB_GL_NAME_p) $(__WXLIB_AUI_NAME_p)
$(__WXLIB_MEDIA_NAME_p) $(__WXLIB_ADV_NAME_p) $(__WXLIB_NET_NAME_p)
$(__WXLIB_XML_NAME_p) $(__
WXLIB_CORE_NAME_p) $(__WXLIB_BASE_NAME_p)
-lwxtiff$(WX3RDPARTYLIBPOSTFIX) -lwxjpeg$(WX3RDPARTYLIBPOSTFIX)
-lwxpng$(WX3RDPARTYLIBPOSTFIX) -lwxz
lib$(WX3RDPARTYLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX)
-lwxexpat$(WX3RDPARTYLIBPOSTFIX) -lkernel32 -luser32 -lgdi32
-lcomdlg32 -lwinspool -lwinmm
 -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32
-lwsock32 -lodbc32
Thanks,
 John Labenski

On 8/1/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> >
> > We link to the wxWidgets GL library since there was a user that was
> > using it. Does dev studio (mingw right?) not allow you to compile the
> > wxWidgets GL library or did you not compile it yourself?
> >
> I use version 7
>
> this library does not compile for window
I think you need to edit wxWidgets/include/wx/msw/setup.h and set
wxUSE_OPENGL 1.
Either that or just remove the lib in the build file.
Unfortunately there's no easy way to allow people to pick and choose
the libs to link to. The code can use #if statements, but there's
nothing equivalent for the linker command.
-John Labenski

On 8/1/07, Ryan Pusztai <rpu...@gm...> wrote:
>
> I think there is a problem because I can't complie it either with mingw
> and I have built the GL (wxmsw28ud_gl.a) libraries.
>
Here is the command line that is produced. Notice that linking to the GL
library is missing.
g++ -o ..\..\..\bin\gcc_lib\wxlua.exe gccmsw\app_wxlua_lconsole.o
gccmsw\app_wxlua_wxlua.o gccmsw\app_wxlua_wxlua_rc.o
-mthreads -LD:\devel\Libraries\wxWidgets2.8\lib\gcc_lib
-L..\..\..\lib\gcc_lib -L..\..\..\modules\lua\lib -Wl,--subsys
tem,windows -mwindows -lwxlua_msw28_wxluasocket -lwxlua_msw28_wxluadebug
-lwxlua_msw28_wxbindadv -lwxlua_msw28_wxbinda
ui -lwxlua_msw28_wxbindbase -lwxlua_msw28_wxbindcore -lwxlua_msw28_wxbindgl
-lwxlua_msw28_wxbindhtml -lwxlua_msw28_wxbin
dmedia -lwxlua_msw28_wxbindnet -lwxlua_msw28_wxbindstc
-lwxlua_msw28_wxbindxml -lwxlua_msw28_wxbindxrc -lwxlua_msw28_wxl
ua -llua5.1 -lwxmsw28_stc -lwxmsw28_xrc -lwxmsw28_html -lwxmsw28_aui
-lwxmsw28_media -lwxmsw28_adv -lwxbase28_net -lwxba
se28_xml -lwxmsw28_core -lwxbase28 -lwxtiff -lwxjpeg -lwxpng -lwxzlib
-lwxregex -lwxexpat -lkernel32 -luser32 -lgdi32 -l
comdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid
-lrpcrt4 -ladvapi32 -lwsock32 -lodbc32
-- 
Regards,
Ryan
RJP Computing

John Labenski <jlabenski@...> writes:
> 
> We link to the wxWidgets GL library since there was a user that was
> using it. Does dev studio (mingw right?) not allow you to compile the
> wxWidgets GL library or did you not compile it yourself?
> 
I use version 7
this library does not compile for window
> 
> How could it? The executable,
> http://wxlua.sourceforge.net/download/wxlua_2007_07_31_exe.zip, was
> compiled directly from the CVS head source code yesterday and so it
> should be identical to the one you compiled? I compiled it using MSVC
> 6, maybe there's a problem with MingW?
> 
I will try again maybe cvs did not work

On 8/1/07, John Labenski <jla...@gm...> wrote:
>
> On 8/1/07, Andre <ar...@ki...> wrote:
> > John Labenski <jlabenski@...> writes:
> > > Ok, that's the current CVS. Hopefully you'll get the same results with
> that.
> >
> > I was able to compile wxlua.exe in dev studio removing the link to the
> gl lib.
>
> We link to the wxWidgets GL library since there was a user that was
> using it. Does dev studio (mingw right?) not allow you to compile the
> wxWidgets GL library or did you not compile it yourself?
>
> > The code still have the same problem.
>
> How could it? The executable,
> http://wxlua.sourceforge.net/download/wxlua_2007_07_31_exe.zip, was
> compiled directly from the CVS head source code yesterday and so it
> should be identical to the one you compiled? I compiled it using MSVC
> 6, maybe there's a problem with MingW?
I think there is a problem because I can't complie it either with mingw and
I have built the GL (wxmsw28ud_gl.a) libraries.
-- 
Regards,
Ryan
RJP Computing

On 8/1/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
> > Ok, that's the current CVS. Hopefully you'll get the same results with that.
>
> I was able to compile wxlua.exe in dev studio removing the link to the gl lib.
We link to the wxWidgets GL library since there was a user that was
using it. Does dev studio (mingw right?) not allow you to compile the
wxWidgets GL library or did you not compile it yourself?
> The code still have the same problem.
How could it? The executable,
http://wxlua.sourceforge.net/download/wxlua_2007_07_31_exe.zip, was
compiled directly from the CVS head source code yesterday and so it
should be identical to the one you compiled? I compiled it using MSVC
6, maybe there's a problem with MingW?
Could you add the wxPrintf statement to this function in
modules/wxlua/src/wxlstate.cpp
I would expect that when the error occurs that the "tag" variable
would be equal to the g_wxluatag_wxLuaFunction tag, but the wxlua_ttag
would return something else. In fact, the wxlua_ttag should always
equal the "tag" variable.
bool LUACALL wxlua_tpushusertag(lua_State *L, const void *u, int tag,
bool track)
{
...
 wxlua_pushkey_wxLuaObjects(L);
 lua_rawget(L, LUA_REGISTRYINDEX); // pop key, push result (the obj table)
 lua_pushlightuserdata(L, (void*)u); // key on Lua's userdata
 lua_rawget(L, -2);
 if (wxlua_iswxuserdata(L, -1))
 {
 wxPrintf(wxT("HELP! %d = %d %d\n"), wxlua_ttag(L, -1), tag,
g_wxluatag_wxLuaFunction);
 lua_remove(L, -2); // remove the obj table
 return true;
 }
Thanks,
 John Labenski

John Labenski <jlabenski@...> writes:
> 
> Ok, that's the current CVS. Hopefully you'll get the same results with that.
> 
I was able to compile wxlua.exe in dev studio removing the link to the gl lib.
The code still have the same problem.

John Labenski <jlabenski@...> writes:
> Ok, that's the current CVS. Hopefully you'll get the same results with that.
> 
cannot link, wxmsw28ud_gl.lib is requested
should probably not happen on window
Andre

John Labenski <jlabenski@...> writes:
>> Ok, that's the current CVS. Hopefully you'll get the same results with that.
> 
cannot link any more wxmsw28ud_gl.lib is requested 
Should this be needed on window?
Andre

On 8/1/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
> >
> > Thats when I made the changes. I'll go over them again.
> >
> > > I will try to narrow it farther (if I can) tomorrow.
> >
> > Could you try this wxLua.exe executable and let me know if it happens with it?
> >
> > http://wxlua.sourceforge.net/download/wxlua_2007_07_31_exe.zip
>
>
> This code works without a problem.
Ok, that's the current CVS. Hopefully you'll get the same results with that.
Thanks,
 John Labenski

John Labenski <jlabenski@...> writes:
> 
> 
> Thats when I made the changes. I'll go over them again.
> 
> > I will try to narrow it farther (if I can) tomorrow.
> 
> Could you try this wxLua.exe executable and let me know if it happens with it?
> 
> http://wxlua.sourceforge.net/download/wxlua_2007_07_31_exe.zip
> 
This code works without a problem.
Andre

Hi,
John Labenski ha scritto:
> On 7/31/07, Francesco Montorsi <f18...@ya...> wrote:
>> John Labenski ha scritto:
>>> I'll try to do a binary release tomorrow, the source will have to wait
>>> since the configure script is still not working.
>> I can give an hand with this release.
>> However I cannot understand why configure script still doesn't work...
>> which errors do you get?
> 
> It has more to do with the extra binding libs. I tried to copy
> everything that the stc module had in the bakefiles, but currently
> only base, core, and stc are made. I'm not sure why base and core work
> since neither existed before and that's why I'm guessing it has
> something to do with configure and that we need checks for the
> existence of all of the libs.
I've found the problem. When adding new options to the options.bkl 
files, also configure.ac needs to be updated accordingly: I've just 
committed the fix and tried to build latest wxLua against wx2.8.4 in 
shared+debug+ansi mode and it works.
I've also modified a bit the bakefiles so that inter-modules 
dependencies are now handled correctly (to avoid e.g. that wxbindnet 
gets built before wxbindbase).
Let me know if it works for you, too.
>> Unfortunately I cannot build wxLua CVS HEAD now because I miss a wx28 on
>> my system (I always use wxTRUNK and that gives troubles because of the
>> string changes). I'm going to checkout wx28 and test a build against
>> that right now btw.
> 
> Thanks, I'll try to get it going with wxWidgets trunk, but I'm afraid
> that there may be some other big changes. I really want to get this
> release out to fix at least one of the bugs first though.
I know, there are various changes in wx3. Given however that wx2.9 is 
not out yet, I think it will elapse a lot of time before wx3 will be 
ready and thus there's no hurry ;)
Francesco