wxlua-users Mailing List for wxLua

> > Doesn't wx have any way of rebooting/loging off the computer?
>
> The cvs version, or next version 2.8.6 coming in the next week or so,
> has wxShutdown().
> http://www.wxwidgets.org/manuals/stable/wx_processfunctions.html#wxshutdown

Awesome! This is great :) But it doesn't seem to offer the possibility
to logoff. However, I found wxExecute that might be able to help me.
It says "If the child process IO is redirected, under Windows the
process window is not shown by default". Can someone please help me
out how to use that information to not show a window when calling
"shutdown -l -t 0"?

On 9/30/07, Tobbe Lundberg <tob...@gm...> wrote:
> > That command window will always appears as far as I know, you can't hide
> > it.
>
> Someone told me to use CreateProcess, but I couldn't figure out how to use it.
>
> Doesn't wx have any way of rebooting/loging off the computer?

The cvs version, or next version 2.8.6 coming in the next week or so,
has wxShutdown().
http://www.wxwidgets.org/manuals/stable/wx_processfunctions.html#wxshutdown

Regards,
    John Labenski

> That command window will always appears as far as I know, you can't hide
> it.

Someone told me to use CreateProcess, but I couldn't figure out how to use it.

Doesn't wx have any way of rebooting/loging off the computer?

That command window will always appears as far as I know, you can't hide  
it. But, on shutdown, it doesn't matter I think :)

Hi

I'm writing a program entirely in lua where the gui part is done with
wxlua. Now I need this program to be able to reboot the computer and
to logoff the current user. This program will only be used on Windows,
so I tried os.execute("shutdown -r -t 0") and os.execute("shutdown -l
-t 0"), and it did work (for Win2000 and WinXP at least), but the
problem is that it flashed a dos prompt on the screen for a split
second. Is there any way to do what I want without having that dos
window showing?

Thanks in advance
//Tobbe

Feature Requests item #1798497, was opened at 2007-09-19 21:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745327&aid=1798497&group_id=140042

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Andre Arpin (andrearpin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Executed frozen programs from any directory

Initial Comment:
Frozen program can only be executed from the directory where they reside or using an explicit path. Also if the extention is no given on widow the file cannot be found.

A revise version of wxluafreeze.cpp is submitted

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745327&aid=1798497&group_id=140042

On 9/5/07, John Labenski <jla...@gm...> wrote:
>
> You're using the wxWidgets monolithic build it seems using mingw?


Yes I am using monolithic MinGW.

Do you use "configure" with mingw or just makefile.gcc?


I am using the makefile.gcc.

The monolithic
> build is broken because nobody's checked it. In fact I don't even know
> what gets put into the monolithic build?


Wow. That is not good. You are planning on fixing that, right? I think the
monolithic dll version is the only way, I personally, would use the dll
version. I don't like having 6+ dll's as dependencies. I could deal with it
for static linking, but I figure, that is just more setup and more setting I
need to set in my main project that will use wxLua. ;-)

If I remember correctly the
> GL lib is not part of it, just like the jpeg lib isn't. Is there a
> list somewhere about what is part of the monolithic build so that we
> can add the extra libs for wxLua to link to?


Good question. I don't have a real need for GL so I never use it, so I
couldn't say. As for jpeg and other image libraries, I think they are
included in the wx dll. I will check for sure when I get back to work
tomorrow.

..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_bind.o):wxgl_bind.cpp:(.data+0xc):
> > undefined reference
> > to `wxGLCanvas::ms_classInfo'
>
> Ok, this says clearly that you need to link to the wxWidgets GL lib
> since it's not part of -lwxmsw28.


I have added that in the location in the makefile where the Bakefile  named
variable is located and I still got the same results. I will double verify
this tomarrow at work and post the errors.

You should have a wxmsw28_gl.lib file (just like -lwxmsw28_stc) in the
> wxWidgets lib dir if you've built it.


Yes. I definatly have it and it is right next to the other build files. What
compilers are actively tested? Is it only VC?

I'll try to find some time to look into it again, but I could not
> figure out how to get bakefile to work right for this before.


That is kind of the point I was driving at in my previous email. Your
project is only as good as your ability to build it.

I should write something about this. There is a little about the
> modules in the wxlua.html file with some comments on what depends on
> what. You need modules/wxlua and modules/wxbind at least. The parts of
> modules/wxbind are exactly like the wxWidgets libs, take the ones you
> want, typically base, core, adv...


That would be a great help. Thanks.

A lot of work has gone into making the bakefiles work as well as they
> do. I personally have a hard time understanding the XML/python nature
> of them, but Francesco does and I believe he is still on vacation. I
> hope he has time to look at this when he gets back. wxLua uses
> bakefile since that's what wxWidgets uses, if it works for them it
> should be able to work for us since we target the same systems and
> compilers.


Yes, I understand that. There is a very massive code base for that. It makes
sense. I just want get a feel for how the project runs.
-- 
Regards,
Ryan
RJP Computing

On 9/5/07, Ryan Pusztai <rpu...@gm...> wrote:
>
> > If I remember correctly the problem is that the build files DO specify
> > the GL lib, but that you haven't built it?
>
> Here is the command line:
> pcrt4 -ladvapi32 -lwsock32 -lodbc32 -llua5.1
> if not exist ..\..\..\bin\gcc_lib mkdir ..\..\..\bin\gcc_lib
> g++ -o ..\..\..\bin\gcc_lib\wxlua.exe gccmsw\app_wxlua_wxlua.o
> gccmsw\app_wxlua_lconsole.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 -lwxtiff -lwxjpeg -lwxpng
> -lwxzlib -lwxregex -lwxexpat -lkernel32 -luser32
> -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32
> -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodb
> c32

You're using the wxWidgets monolithic build it seems using mingw? Do
you use "configure" with mingw or just makefile.gcc? The monolithic
build is broken because nobody's checked it. In fact I don't even know
what gets put into the monolithic build? If I remember correctly the
GL lib is not part of it, just like the jpeg lib isn't. Is there a
list somewhere about what is part of the monolithic build so that we
can add the extra libs for wxLua to link to?
 ..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_bind.o):wxgl_bind.cpp:(.data+0xc):
> undefined reference
> to `wxGLCanvas::ms_classInfo'

Ok, this says clearly that you need to link to the wxWidgets GL lib
since it's not part of -lwxmsw28.

> How do I tell if this is the case? I  have built the wxGL library, so I
> don't know. I have also defined #define wxUSE_GLCANVAS       1 in "
> setup.h". I have not touched any files in the wxLua source archive. I have
> set the environment variable WXWIN to my wxWidgets install root directory.
> Am I missing anything else?

You should have a wxmsw28_gl.lib file (just like -lwxmsw28_stc) in the
wxWidgets lib dir if you've built it.

> I am trying to determine how I am going to maintain this issue. If I edit
> the files in wxLua, that means I can't external to the sources, once you
> move to using SVN. Plus I don't want to maintain this for the lifetime of my
> project.

I'll try to find some time to look into it again, but I could not
figure out how to get bakefile to work right for this before.

> Can you tell me what the bare minimum things are to use wxLua in my
> application? Can you tell me what the bare minimum things required for using
> wxLua as a Lua module? I think it starts to get into this in the
> installation document, but I am still trying to build the entire package,
> because usually makefiles are easy to build from.

I should write something about this. There is a little about the
modules in the wxlua.html file with some comments on what depends on
what. You need modules/wxlua and modules/wxbind at least. The parts of
modules/wxbind are exactly like the wxWidgets libs, take the ones you
want, typically base, core, adv...

> <A personal sidebar discussion> (These are only thoughts not criticisms)
> I am just asking, is BakeFile the way that you prefer to build wxLua. If
> not, is the person that set them up going to return? I started using
> BakeFile a couple of years ago and found it extremely complicated. So much
> so that I can't even attempt to fix these issues I am having, in the place
> where I believe the problem comes from, the BakeFiles. I do not mean any
> disrespect and only ask to see if I can help figure out a bulletproof way of
> building wxLua. It is so crucial for a package such as wxLua to be easy to
> build because it is going to have the ability to be embedded in a users
> application.
> Your thoughts and remarks?
> <End personal sidebar discussion>

A lot of work has gone into making the bakefiles work as well as they
do. I personally have a hard time understanding the XML/python nature
of them, but Francesco does and I believe he is still on vacation. I
hope he has time to look at this when he gets back. wxLua uses
bakefile since that's what wxWidgets uses, if it works for them it
should be able to work for us since we target the same systems and
compilers.

Regards,
    John

I noticed you didn't have a -l option for the wx GL library in that command=
 output you posted. Can you post the result when this was included?

Also, if you've tried putting a -l option for the wx GL library into the co=
mmand line and you still get unresolved references, it might then just be t=
he old problem of the order of the libraries. You could try entering the co=
mmand directly on the command line and trying the -l option at different po=
sitions.

Darwin

_________________________________________________________________
Feel like a local wherever you go.
http://www.backofmyhand.com=

On 9/5/07, Ryan Pusztai <rpu...@gm...> wrote:
>
> On 9/5/07, Darwin Slattery <dar...@ho...> wrote:
> >
> >
> > I'm not sure if you're having the same problem as I was but if it's
> > related to unresolved reference errors for the wxGL* classes then I found it
> > was just a case of adding the GL library to the makefile. This is only
> > applicable to builds using the make system of course.
> >
> > Have a look in your wxWidgets library directory and identify the name of
> > the GL library. In my case it was called 'libwx_gtk2ud_gl-2.8.so'. Add
> > the text '-lwx_gtk2ud_gl-2.8' to the WX_LIBS variable in the file
> > apps/Makefile.
> >
> > Hopefully this will get you by while you're waiting for a patch,
> > Darwin
> >
>
> I will try this and let you know. Thanks.


This did not work. I still get build problems. Still trying more things. Boy
this used to work that is why it is so mysterious.
-- 
Regards,
Ryan
RJP Computing

On 9/5/07, John Labenski <jla...@gm...> wrote:
>
> On 8/31/07, Ryan Pusztai <rpu...@gm...> wrote:
> > I hate to ask this because I am a developer of other open-source project
> and
> > know what a pain this type of question can introduce;
>
> Ugh. :)


;-)

If I remember correctly the problem is that the build files DO specify
> the GL lib, but that you haven't built it?


Here is the command line:
pcrt4 -ladvapi32 -lwsock32 -lodbc32 -llua5.1
if not exist ..\..\..\bin\gcc_lib mkdir ..\..\..\bin\gcc_lib
g++ -o ..\..\..\bin\gcc_lib\wxlua.exe gccmsw\app_wxlua_wxlua.o
gccmsw\app_wxlua_lconsole.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 -lwxtiff -lwxjpeg -lwxpng
-lwxzlib -lwxregex -lwxexpat -lkernel32 -luser32
-lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32
-loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodb
c32
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_bind.o):wxgl_bind.cpp:(.data+0xc):
undefined reference
to `wxGLCanvas::ms_classInfo'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_bind.o):wxgl_bind.cpp:(.data+0x30):
undefined reference
 to `wxGLContext::ms_classInfo'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0xce):
undefined reference to
`wxGLCanvas::SetColour(char const*)'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0x3c1):
undefined reference to
 `wxGLCanvas::wxGLCanvas(wxWindow*, wxGLCanvas const*, int, wxPoint const&,
wxSize const&, long, wxString const&, int*,
wxPalette const&)'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0x749):
undefined reference to
 `wxGLCanvas::wxGLCanvas(wxWindow*, int, int*, wxPoint const&, wxSize
const&, long, wxString const&, wxPalette const&)'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0x99d):
undefined reference to
 `wxGLCanvas::SwapBuffers()'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0xa4d):
undefined reference to
 `wxGLCanvas::SetCurrent()'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0xb1c):
undefined reference to
 `wxGLCanvas::SetCurrent(wxGLContext const&) const'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0xde9):
undefined reference to
 `wxGLContext::wxGLContext(wxGLCanvas*, wxGLContext const*)'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0xeec):
undefined reference to
 `wxGLContext::SetCurrent(wxGLCanvas const&) const'
..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0x1269):
undefined reference t
o `wxGLCanvas::wxGLCanvas(wxWindow*, int, wxPoint const&, wxSize const&,
long, wxString const&, int*, wxPalette const&)'

..\..\..\lib\gcc_lib/libwxlua_msw28_wxbindgl.a(wxbindgl_lib_wxgl_gl.o):wxgl_gl.cpp:(.text+0x15f1):
undefined reference t
o `wxGLCanvas::wxGLCanvas(wxWindow*, wxGLContext const*, int, wxPoint
const&, wxSize const&, long, wxString const&, int*
, wxPalette const&)'
collect2: ld returned 1 exit status
mingw32-make.exe[1]: *** [..\..\..\bin\gcc_lib\wxlua.exe] Error 1
mingw32-make.exe[1]: Leaving directory `D:/devel/lua/wxLua/apps/build/msw'
mingw32-make.exe: *** [apps] Error 2

How do I tell if this is the case? I  have built the wxGL library, so I
don't know. I have also defined #define wxUSE_GLCANVAS       1 in "setup.h".
I have not touched any files in the wxLua source archive. I have set the
environment variable WXWIN to my wxWidgets install root directory. Am I
missing anything else?

If this is the case then
> it's easy;
> 1) Edit the build file you use and just remove the linking dependency
> for the GL lib.
>     This takes a little bit of digging, but it shouldn't be hard,
> search for "GL"
> 2) Edit modules/wxbind/setup/wxluasetup.h and put "wxLUA_USE_wxGLCanvas 0"
> 3) Don't call wxLuaBinding_wxgl_init()


I am trying to determine how I am going to maintain this issue. If I edit
the files in wxLua, that means I can't external to the sources, once you
move to using SVN. Plus I don't want to maintain this for the lifetime of my
project.

Can you tell me what the bare minimum things are to use wxLua in my
application? Can you tell me what the bare minimum things required for using
wxLua as a Lua module? I think it starts to get into this in the
installation document, but I am still trying to build the entire package,
because usually makefiles are easy to build from.

<A personal sidebar discussion> (These are only thoughts not criticisms)
I am just asking, is BakeFile the way that you prefer to build wxLua. If
not, is the person that set them up going to return? I started using
BakeFile a couple of years ago and found it extremely complicated. So much
so that I can't even attempt to fix these issues I am having, in the place
where I believe the problem comes from, the BakeFiles. I do not mean any
disrespect and only ask to see if I can help figure out a bulletproof way of
building wxLua. It is so crucial for a package such as wxLua to be easy to
build because it is going to have the ability to be embedded in a users
application.
Your thoughts and remarks?
<End personal sidebar discussion>
--
Regards,
Ryan
RJP Computing

On 8/31/07, Ryan Pusztai <rpu...@gm...> wrote:
> I hate to ask this because I am a developer of other open-source project and
> know what a pain this type of question can introduce;

Ugh. :)

> When are the build problems going to be fixed? I need to use wxLua in a
> project but I can't build it because of the OpenGL dependency problem in the
> BakeFiles. Any update, even if it is "go jump in a lake", is ok. I am just
> trying to see if I need to find another solution for my project. Thanks so
> much for all your effort.

The problem with the GL and other libraries are that you cannot select
them if you build in a GUI like MSVC. So, to some extent it's easier
to have them on since I would imagine that it's easier to remove the
-lwxlibglxyz line than try to add it back.

If I remember correctly the problem is that the build files DO specify
the GL lib, but that you haven't built it? If this is the case then
it's easy;
1) Edit the build file you use and just remove the linking dependency
for the GL lib.
    This takes a little bit of digging, but it shouldn't be hard,
search for "GL"
2) Edit modules/wxbind/setup/wxluasetup.h and put "wxLUA_USE_wxGLCanvas 0"
3) Don't call wxLuaBinding_wxgl_init()

Hope this helps,
    John

On 9/5/07, Darwin Slattery <dar...@ho...> wrote:
>
>
> I'm not sure if you're having the same problem as I was but if it's
> related to unresolved reference errors for the wxGL* classes then I found it
> was just a case of adding the GL library to the makefile. This is only
> applicable to builds using the make system of course.
>
> Have a look in your wxWidgets library directory and identify the name of
> the GL library. In my case it was called 'libwx_gtk2ud_gl-2.8.so'. Add the
> text '-lwx_gtk2ud_gl-2.8' to the WX_LIBS variable in the file
> apps/Makefile.
>
> Hopefully this will get you by while you're waiting for a patch,
> Darwin
>

I will try this and let you know. Thanks.
-- 
Regards,
Ryan
RJP Computing

I'm not sure if you're having the same problem as I was but if it's related=
 to unresolved reference errors for the wxGL* classes then I found it was j=
ust a case of adding the GL library to the makefile. This is only applicabl=
e to builds using the make system of course.

Have a look in your wxWidgets library directory and identify the name of th=
e GL library. In my case it was called 'libwx_gtk2ud_gl-2.8.so'. Add the te=
xt '-lwx_gtk2ud_gl-2.8' to the WX_LIBS variable in the file apps/Makefile.

Hopefully this will get you by while you're waiting for a patch,
Darwin

_________________________________________________________________
Feel like a local wherever you go.
http://www.backofmyhand.com=