wxlua-users Mailing List for wxLua

On 4/28/07, Kees Jongenburger <kee...@gm...> wrote:
> On 4/27/07, John Labenski <jla...@gm...> wrote:
> > On 4/27/07, Kees Jongenburger <kee...@gm...> wrote:
> > > Hello
> > >
> > > I have created a small sample of using wxLua with xrc file.
> > > The example is really trivial but I think it really show the power the
> > > lua/wx/xrc combo
> > >
> > > I would like such a sample to be in the samples directory
> >
> > We have the calculator sample already, is it not clear enough? If you
> > really think that having a very simple xrc sample would help, that's
> > fine and I'll add it, I just want to make sure that it makes sense.
>
> I have seen the calculator sample that exactly what made me go "OK
> lets look into this"
> This is why i spent a little more time getting things working.
> Here is what happened. Of course I did not read the documentation
hum... See the section at the bottom about the wxLua apps.
http://wxlua.sourceforge.net/documentation.php
http://wxlua.sourceforge.net/docs/wxlua.html
Ok, so the problem was just how to run the samples. So... I won't add
your sample, but of course it is easy to get to using the mailing list
so people can still try it out. If you happen to write something a
little more advanced that's be great.
> you know , perhaps just adding a bit of documentation inside the
> samples telling how to run them would be enough)
> , I did not know at that point that there was a wxlua command. I
> think my sample make sence.
> I would be willing to create a few sample usages of the same sample
> (embeded , stantalone running with lua and running with wxlua) I would
> have given me a hint on how to use wxLua.
I'd rather not add how to run the programs to all the samples. I'd
rather make people read the docs I wrote so they have a better
understanding about what is going on.
However, I will add a separate section in the docs on how to run the
samples and trust that people will read it. :)
> > Can I use your screenshot on wxlua.sf.net? Could you give some details
> > about it, eg. what phone (Nokia N700 right?), you're using an emulator
> > I guess (which one?), etc.
> This was a screen shot taken from the actual device (using x11vnc).
> since it is linux based it is not really an emulator but there is the
> maemo.org website
> where you can download a sdk, after that you can compile and test programs
> on your linux machine by running a small x server (Xephyr) and
> starting the maemo desktop.
>
> If still interesting for you feel free to ask for more. I would like
> to provide .deb package for the nokia 770 and N800 if possible with
> running samples
Sure. Whenever you think that things work well. I recommend that you
use the CVS version of wxLua in that case since I try to make sure
that it always works and is more up-to-date than the releases (which
we should do more of...).
Regards,
 John Labenski

On 4/28/07, Kees Jongenburger <kee...@gm...> wrote:
> On 4/28/07, Ryan Pusztai <rpu...@gm...> wrote:
> > > package.cpath =
> > >
> > ";;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;"
> > > require("wx")
> > >
> > > and
> > > wx.wxGetApp():MainLoop()
> >
> > This is incredible. I didn't know you could do that. That would be a great
> > example to have as well.
> At least this sample helped someone
>
See wxLua/samples/luamodule.wx.lua and also
wxLua/util/wrapmodule/wrapmodule.wx.lua for using a vanilla lua and
wx.dll as a lua module using "require".
Yes... this should be better documented in a section called "How to
run the samples."
Regards,
 John Labenski

On 4/28/07, Ryan Pusztai <rpu...@gm...> wrote:
> > package.cpath =
> >
> ";;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;"
> > require("wx")
> >
> > and
> > wx.wxGetApp():MainLoop()
>
> This is incredible. I didn't know you could do that. That would be a great
> example to have as well.
At least this sample helped someone
greetings

On 4/28/07, Kees Jongenburger <kee...@gm...> wrote:
> I have seen the calculator sample that exactly what made me go "OK
> lets look into this"
> This is why i spent a little more time getting things working.
> Here is what happened. Of course I did not read the documentation
> and after building wxLua I went to the samples directory I saw
> that the files had a lua extension so I assumed I could run them
> from the command line by using the lua command. That did not work
> for all only luamodule.wx.lua worked. So I stated adding
>
> package.cpath =
>
> ";;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;"
> require("wx")
>
> and
> wx.wxGetApp():MainLoop()
This is incredible. I didn't know you could do that. That would be a great
example to have as well.
to all the samples really thinking it was kind of weird that the
> samples did not work
> and I assumed them to be outdated. Of course the best thing is to blame me
> for
> not being smart :p but this was my first encounter with wxLua(just so
> you know , perhaps just adding a bit of documentation inside the
> samples telling how to run them would be enough)
> , I did not know at that point that there was a wxlua command. I
> think my sample make sence.
> I would be willing to create a few sample usages of the same sample
> (embeded , stantalone running with lua and running with wxlua) I would
> have given me a hint on how to use wxLua.
I think more examples that are small and to the point would really help me
to learn the power of wxLua.
-- 
Regards,
Ryan
RJP Computing

On 4/27/07, John Labenski <jla...@gm...> wrote:
> On 4/27/07, Kees Jongenburger <kee...@gm...> wrote:
> > Hello
> >
> > I have created a small sample of using wxLua with xrc file.
> > The example is really trivial but I think it really show the power the
> > lua/wx/xrc combo
> >
> > I would like such a sample to be in the samples directory
>
> We have the calculator sample already, is it not clear enough? If you
> really think that having a very simple xrc sample would help, that's
> fine and I'll add it, I just want to make sure that it makes sense.
I have seen the calculator sample that exactly what made me go "OK
lets look into this"
This is why i spent a little more time getting things working.
Here is what happened. Of course I did not read the documentation
and after building wxLua I went to the samples directory I saw
that the files had a lua extension so I assumed I could run them
from the command line by using the lua command. That did not work
for all only luamodule.wx.lua worked. So I stated adding
package.cpath =
";;../lib/?.so;../lib/vc_dll/?.dll;../lib/bcc_dll/?.dll;../lib/mingw_dll/?.dll;"
require("wx")
and
wx.wxGetApp():MainLoop()
to all the samples really thinking it was kind of weird that the
samples did not work
and I assumed them to be outdated. Of course the best thing is to blame me for
not being smart :p but this was my first encounter with wxLua(just so
you know , perhaps just adding a bit of documentation inside the
samples telling how to run them would be enough)
, I did not know at that point that there was a wxlua command. I
think my sample make sence.
 I would be willing to create a few sample usages of the same sample
(embeded , stantalone running with lua and running with wxlua) I would
have given me a hint on how to use wxLua.
> The calc sample has some code for helping the user find the xrc code
> which is very nice since otherwise the sample seems "broken" if the
> xrc file can't be found. This happens if you run it from the
> wxLuaEditor since the current working directory will be wrong unless
> you started wxLuaEdit from the same dir that the xrc file is in.
See my comments above , they way I looked at the none of the samples
where working.
>
> > p.s. I also posted a while ago about xwLua
> > http://www.maemopeople.org/index.php/keesj/2007/02/07/p49#more49
> > It might be rewarding to know wxLua was running on the maemo platform
>
> That's very cool, I didn't know that wxWidgets worked on phones!
The Nokia 770 and N800 are not phones but internet tablets(you can not make
gprs phone calls with them) They run a small linux distro a x server ,
gtk etc(moost of the stuff is open source). So I don't know if wxLua will work
 on simbian phones
>
> Can I use your screenshot on wxlua.sf.net? Could you give some details
> about it, eg. what phone (Nokia N700 right?), you're using an emulator
> I guess (which one?), etc.
This was a screen shot taken from the actual device (using x11vnc).
since it is linux based it is not really an emulator but there is the
maemo.org website
where you can download a sdk, after that you can compile and test programs
on your linux machine by running a small x server (Xephyr) and
starting the maemo desktop.
If still interesting for you feel free to ask for more. I would like
to provide .deb package for the nokia 770 and N800 if possible with
running samples
greetings

On 4/27/07, Kees Jongenburger <kee...@gm...> wrote:
> Hello
>
> I have created a small sample of using wxLua with xrc file.
> The example is really trivial but I think it really show the power the
> lua/wx/xrc combo
>
> I would like such a sample to be in the samples directory
We have the calculator sample already, is it not clear enough? If you
really think that having a very simple xrc sample would help, that's
fine and I'll add it, I just want to make sure that it makes sense.
The calc sample has some code for helping the user find the xrc code
which is very nice since otherwise the sample seems "broken" if the
xrc file can't be found. This happens if you run it from the
wxLuaEditor since the current working directory will be wrong unless
you started wxLuaEdit from the same dir that the xrc file is in.
> p.s. I also posted a while ago about xwLua
> http://www.maemopeople.org/index.php/keesj/2007/02/07/p49#more49
> It might be rewarding to know wxLua was running on the maemo platform
That's very cool, I didn't know that wxWidgets worked on phones!
Can I use your screenshot on wxlua.sf.net? Could you give some details
about it, eg. what phone (Nokia N700 right?), you're using an emulator
I guess (which one?), etc.
Thanks,
 John Labenski

Even that did not help, i am left with a gray dialog, which has the proper size, but does not show anything but a toolbar.
But in wxLua i found somewhere this:
 SetSizeHints(wxSize(400, 400));
 GetSizer()->Fit(this);
 GetSizer()->SetSizeHints(this);
 Centre();
 // The size of the frame isn't set when the splitter is created, resize it
 wxSplitterWindow *splitWin = m_luaConsole->GetSplitterWin();
 splitWin->SetSashPosition( splitWin->GetSize().y/2 );
Don't ask me why it works, but it does :-)
Thanks,
klaas
John Labenski wrote:
> 
> m_luaConsole->SetInitialSize(wxSize(400,400);
> 
> and/or
> 
> m_luaConsole->SetMinSize(wxSize(400,400);
-- 
Unclassified

Hello
I have created a small sample of using wxLua with xrc file.
The example is really trivial but I think it really show the power the
lua/wx/xrc combo
I would like such a sample to be in the samples directory
greetings
p.s. I also posted a while ago about xwLua
http://www.maemopeople.org/index.php/keesj/2007/02/07/p49#more49
It might be rewarding to know wxLua was running on the maemo platform
here is the sample
--layout.xrc
<?xml version="1.0" encoding="ascii"?>
<resource>
 <object class="wxFrame" name="ID_FRAME">
 <title></title>
 <object class="wxButton" name="ID_BUTTON">
 <label>Hello</label>
 </object>
 </object>
</resource>
--main.lua
#!/usr/bin/wxlua
frame = nil
xmlResource = nil
function error(message)
 wx.wxMessageBox(message,"",wx.wxOK + wx.wxICON_EXCLAMATION,wx.wxNull)
end
function buttonClicked(event)
 event:Skip()
 frame:Destroy()
 frame:Show(false)
end
function main()
 xmlResource = wx.wxXmlResourceGetDefault()
 xmlResource:InitAllHandlers()
 --layout.xrc was create with xrced
 xmlResource:Load("layout.xrc")
 frame = xmlResource:CreateFrame( wx.wxNull, "ID_FRAME")
 if not frame then
 error("Error loading xrc resources!");
 return
 end
 ID_BUTTON = xmlResource:GetXRCID("ID_BUTTON")
 frame:Connect(ID_BUTTON, wx.wxEVT_COMMAND_BUTTON_CLICKED, buttonClicked)
 frame:Show(true)
end
main()

On 4/27/07, Klaas Holwerda <db...@nl...> wrote:
> Hi John,
>
> If i put in the piece of code down here the wxListBox as control and instead of the m_luaConsole.
> The dialog sizes to the listbox nicely.
> But for some reason wxLuaIDE refuses to this, in fact the dialog is reduced to 0 height.
>
> Do you have any idea why there is this difference?
It probably has something to do with
GetBestSize/GetBestFittingSize/GetMinSize etc... There was a change in
these recently that I didn't follow too closely and have always been
confused by what they really do. In your case however, the min size
should be set to 400x400 since that's what used to happen.
Try the code out below?
Hope this helps,
 John Labenski
> a2dLuaExecDlg::a2dLuaExecDlg( a2dLuaWrapper* commandProcessor, wxFrame* parent, const wxString& title,long style, const
> wxString& name):
> wxDialog(parent,-1,title,wxDefaultPosition,wxDefaultSize,style,name)
> {
> m_parent = parent;
>
> wxBoxSizer* itemBoxSizer = new wxBoxSizer(wxVERTICAL);
> SetSizer(itemBoxSizer);
>
> m_luaConsole = new wxLuaIDE( this, wxID_ANY, wxDefaultPosition,wxSize(400,400) );
 m_luaConsole->SetInitialSize(wxSize(400,400);
and/or
 m_luaConsole->SetMinSize(wxSize(400,400);
> itemBoxSizer->Add(m_luaConsole, 1, wxGROW|wxALL, 0);
>
> //wxListBox* listbox = new wxListBox( this, -1, wxDefaultPosition, wxSize(100,500), 0, NULL,
> wxLB_SINGLE|wxLB_NEEDED_SB );
> //itemBoxSizer->Add(listbox, 1, wxGROW|wxALL, 0);
>
> GetSizer()->FitInside(this);
> GetSizer()->SetSizeHints(this);
> Centre();
> }
>

Hi John,
If i put in the piece of code down here the wxListBox as control and instead of the m_luaConsole.
The dialog sizes to the listbox nicely.
But for some reason wxLuaIDE refuses to this, in fact the dialog is reduced to 0 height.
Do you have any idea why there is this difference?
Thanks,
Klaas
a2dLuaExecDlg::a2dLuaExecDlg( a2dLuaWrapper* commandProcessor, wxFrame* parent, const wxString& title,long style, const 
wxString& name):
	wxDialog(parent,-1,title,wxDefaultPosition,wxDefaultSize,style,name)
{
	m_parent = parent;
 wxBoxSizer* itemBoxSizer = new wxBoxSizer(wxVERTICAL);
 SetSizer(itemBoxSizer);
 m_luaConsole = new wxLuaIDE( this, wxID_ANY, wxDefaultPosition,wxSize(400,400) );
 itemBoxSizer->Add(m_luaConsole, 1, wxGROW|wxALL, 0);
 //wxListBox* listbox = new wxListBox( this, -1, wxDefaultPosition, wxSize(100,500), 0, NULL, 
wxLB_SINGLE|wxLB_NEEDED_SB );
 //itemBoxSizer->Add(listbox, 1, wxGROW|wxALL, 0);
 GetSizer()->FitInside(this);
 GetSizer()->SetSizeHints(this);
 Centre();
}
-- 
Unclassified

Hi,
John Labenski ha scritto:
> On 4/23/07, John Labenski <jla...@gm...> wrote:
>>> 4) probably introduces some new problems with the build system ;)
> 
> MSVC6 wxWidgets 2.8 cvs branch.
> 
> Debug Multilib generates these libs, shouldn't they be in ./lib/vc_lib
> and also for Debug be wxlua_msw28d_XXX.lib?
yes, they should. I should have fixed it now (but I'm on Linux right now 
and cannot test it yet).
> In fact "Release Multilib"
> generates wxlua_msw28d_XXX.lib, so Debug and Release are backwards.
ops. Dummy error from my side. Actually I swapped the BUILD option 
values descriptions so that BUILD==debug was labeled as "release". Fixed 
 now.
Thanks,
Francesco

John Labenski ha scritto:
> On 4/23/07, Francesco Montorsi <f18...@ya...> wrote:
>> Hi all,
>> I'm going to check in a big modification to wxLua bakefiles which:
>>
>> 1) removes wxhacks.bkl and all wxLua's workarounds for wxWidgets
>> presets. wx29 and higher ships with a set of very-well designed
>> wxpresets which (finally) make it easy for wx-based libs like wxLua to
>> use same build conventions (same output naming paths, same output
>> library naming, etc etc).
> 
> Will it still work for 2.8?
yes, to make sure to use the latest wxpresets which however do work with 
wx28, I've put the wxpresets in wxLua CVS.
They are quite stable now and thus they shouldn't go out-of-sync with 
wx's ones easily.
> What bakefile can we use for it? There are
> two different frm-bakefile.tar.gz on SF htdocs and htdocs/bakefile are
> either of these valid?
ouch sorry. I've removed the wrong one. The correct one is that in 
htdocs/bakefile.
Francesco

On 4/23/07, John Labenski <jla...@gm...> wrote:
> > 4) probably introduces some new problems with the build system ;)
MSVC6 wxWidgets 2.8 cvs branch.
Debug Multilib generates these libs, shouldn't they be in ./lib/vc_lib
and also for Debug be wxlua_msw28d_XXX.lib? In fact "Release Multilib"
generates wxlua_msw28d_XXX.lib, so Debug and Release are backwards.
I thought all the libs should be generated in wxLua/lib/... and not
anywhere else?
./modules/build/lib/vc_lib/lua5.1.idb
./modules/build/lib/vc_lib/lua5.1.lib
./modules/build/lib/vc_lib/wxlua_msw28_wxbind.idb
./modules/build/lib/vc_lib/wxlua_msw28_wxbind.lib
./modules/build/lib/vc_lib/wxlua_msw28_wxbindstc.idb
./modules/build/lib/vc_lib/wxlua_msw28_wxbindstc.lib
./modules/build/lib/vc_lib/wxlua_msw28_wxlua.idb
./modules/build/lib/vc_lib/wxlua_msw28_wxlua.lib
./modules/build/lib/vc_lib/wxlua_msw28_wxluadebug.idb
./modules/build/lib/vc_lib/wxlua_msw28_wxluadebug.lib
./modules/build/lib/vc_lib/wxlua_msw28_wxluasocket.idb
./modules/build/lib/vc_lib/wxlua_msw28_wxluasocket.lib
The apps, wxluaedit Debug Multilib for example, links to
wxlua_msw28_wxlua.lib not wxlua_msw28d_wxlua.lib (again Release and
Debug are backwards) and the search paths are:
/libpath:"$(WXWIN)\lib\vc_lib"
/libpath:"..\..\..\lib\vc_lib"
/libpath:"..\..\..\modules\lua\lib"
Thanks,
 John Labenski

On 4/23/07, Francesco Montorsi <f18...@ya...> wrote:
> Hi all,
> FYI just some quick news for those who don't read wx-dev too often ;)
>
> 1) in wx >= 2.9 the Unicode/ANSI build modes will be merged. wx will
> use the best internal representation for wxString depending on the
> underlying platform (e.g. UTF8 for wxGTK, UTF16 for wxMSW).
> => we'll have to update once again all our internal lua<->wxWidgets
> string conversion stuff
Ugh more unicode stuff. :) Actually, I have read some of those
threads and it seems like it will be simpler.
> 2) in wx >= 2.9 contrib folder does not exist anymore. Scintilla is
> now a main wx lib and this is a big bonus for us. It means that we'll be
> able to cut-off some special checks we needed for this contrib and that
> users with a "default" wxWidgets build will be able to get a "more
> complete" wxLua (i.e. wxLuaApp will always be built, wxLuaEdit will
> still need a 3rd party dependency though).
Good.
> 3) in wx >= 2.9, _if_ my SoC project goes well, the old RTTI system of
> wx will be replaced by XTI (eXtended RTTI) which will allow automatic
> generation of wrappers for various wxWidgets classes, in particular
> wxControl-derived ones.
>
> More in details: we'll be able to write a small app which uses some
> wxClassInfo::GetListOfClass(), wxClassInfo::GetClassInterface or similar
> which will allow us to automatically write (at least a portion of) our
> .i files.
That would be nice. I've been thinking about adding some introspection
for lua scripts to get some information about the bindings to use as
help, autocompletion in an editor, or whatever.
-John Labenski

On 4/23/07, Francesco Montorsi <f18...@ya...> wrote:
> Hi all,
> I'm going to check in a big modification to wxLua bakefiles which:
>
> 1) removes wxhacks.bkl and all wxLua's workarounds for wxWidgets
> presets. wx29 and higher ships with a set of very-well designed
> wxpresets which (finally) make it easy for wx-based libs like wxLua to
> use same build conventions (same output naming paths, same output
> library naming, etc etc).
Will it still work for 2.8? What bakefile can we use for it? There are
two different frm-bakefile.tar.gz on SF htdocs and htdocs/bakefile are
either of these valid?
> 2) removes the DSP/DSW files from the "msw" subfolders and rather put
> them into "msvc6" folders.
>
> 3) adds support for MSVC 2005 and puts the VCPROJ/SLN files in the new
> "msvc8" folders.
ok.
> 4) probably introduces some new problems with the build system ;)
>
> I've tested the build system successfully under Linux and I'm going to
> test it again under win32 tomorrow.
>
> If you find any problem with the new makefiles, please let me know.
I can try with VC6 2.8 tomorrow.
Thanks,
 John Labenski

Hi all,
 FYI just some quick news for those who don't read wx-dev too often ;)
 1) in wx >= 2.9 the Unicode/ANSI build modes will be merged. wx will 
use the best internal representation for wxString depending on the 
underlying platform (e.g. UTF8 for wxGTK, UTF16 for wxMSW).
 => we'll have to update once again all our internal lua<->wxWidgets 
string conversion stuff
 2) in wx >= 2.9 contrib folder does not exist anymore. Scintilla is 
now a main wx lib and this is a big bonus for us. It means that we'll be 
able to cut-off some special checks we needed for this contrib and that 
users with a "default" wxWidgets build will be able to get a "more 
complete" wxLua (i.e. wxLuaApp will always be built, wxLuaEdit will 
still need a 3rd party dependency though).
 3) in wx >= 2.9, _if_ my SoC project goes well, the old RTTI system of 
wx will be replaced by XTI (eXtended RTTI) which will allow automatic 
generation of wrappers for various wxWidgets classes, in particular 
wxControl-derived ones.
More in details: we'll be able to write a small app which uses some 
wxClassInfo::GetListOfClass(), wxClassInfo::GetClassInterface or similar 
which will allow us to automatically write (at least a portion of) our 
.i files.
Francesco

Hi all,
 I'm going to check in a big modification to wxLua bakefiles which:
 1) removes wxhacks.bkl and all wxLua's workarounds for wxWidgets 
presets. wx29 and higher ships with a set of very-well designed 
wxpresets which (finally) make it easy for wx-based libs like wxLua to 
use same build conventions (same output naming paths, same output 
library naming, etc etc).
 2) removes the DSP/DSW files from the "msw" subfolders and rather put 
them into "msvc6" folders.
 3) adds support for MSVC 2005 and puts the VCPROJ/SLN files in the new 
"msvc8" folders.
 4) probably introduces some new problems with the build system ;)
I've tested the build system successfully under Linux and I'm going to 
test it again under win32 tomorrow.
If you find any problem with the new makefiles, please let me know.
Thanks,
Francesco

John Labenski ha scritto:
> If you try to compile for debug multilib you get the warning below,
> which means that the program will crash trying to free() anything
> that's malloced since we've mixed debug and non-debug libs.
> 
> Linker Tools Warning LNK4098
> defaultlib "library" conflicts with use of other libs; use /NODEFAULTLIB:library
> 
> We can solve this by adding this
> 
> /NODEFAULTLIB:msvcrt.lib
...
> 
> I would guess that the reason why we need to do this (wxWidgets
> samples do not) is that modules_mod_lua.dsp generates a non-debug
> lua5.1.lib for the "debug" setting and MSVC gets confused and ignores
> the fact that we've set "Use_Debug_Libraries 1" and links to the
> non-debug msvcrt lib? When I change the lua5.1.lib to be debug by hand
> I no longer get the 4098 warning and the program doesn't crash, so I
> think my theory is correct.
Great, thanks for testing/debugging this!
> Francesco, what do you think about this and which way makes more
> sense, add NODEFAULTLIB or change lua5.1.lib to be debug as well?
I really think NODEFAULTLIB is a sort of hack. If user selected 
BUILD=debug, then we need to build lua in DEBUG mode as well.
I should have fixed it now (see also my other mail "Big build system 
changes").
Francesco

Hi all,
 I'm sorrry I'm in a hurry now... I'll look at this issue and read 
mails asap... hang in.
Francesco
Andre ha scritto:
> John Labenski <jlabenski@...> writes:
> 
>> ===============
>> Francesco, what do you think about this and which way makes more
>> sense, add NODEFAULTLIB or change lua5.1.lib to be debug as well?
>>
>> Regards,
>> John Labenski
>>
> 
> This hopefully will also fix the .dsp files.
> 
> I always compile with 
> 
> mk LDFLAGS="/NODEFAULTLIB:\"libc.lib\" /NODEFAULTLIB:\"libcmt.lib\"
> /NODEFAULTLIB:\"msvcrt.lib\" /NODEFAULTLIB:\"libcd.lib\"
> /NODEFAULTLIB:\"libcmtd.lib\""
> 
>>From what you are saying only the msvcrt.lib needs to be removed.
> 
> Is the bakefile still generated using the unreleased version of bakefile.exe?
> 
> Andre
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/

John Labenski <jlabenski@...> writes:
> ===============
> Francesco, what do you think about this and which way makes more
> sense, add NODEFAULTLIB or change lua5.1.lib to be debug as well?
> 
> Regards,
> John Labenski
> 
This hopefully will also fix the .dsp files.
I always compile with 
mk LDFLAGS="/NODEFAULTLIB:\"libc.lib\" /NODEFAULTLIB:\"libcmt.lib\"
/NODEFAULTLIB:\"msvcrt.lib\" /NODEFAULTLIB:\"libcd.lib\"
/NODEFAULTLIB:\"libcmtd.lib\""
>From what you are saying only the msvcrt.lib needs to be removed.
Is the bakefile still generated using the unreleased version of bakefile.exe?
Andre

If you try to compile for debug multilib you get the warning below,
which means that the program will crash trying to free() anything
that's malloced since we've mixed debug and non-debug libs.
Linker Tools Warning LNK4098
defaultlib "library" conflicts with use of other libs; use /NODEFAULTLIB:library
We can solve this by adding this
/NODEFAULTLIB:msvcrt.lib
to the linker lines for all the apps dsp files for the debug setting.
For example in apps_app_wxluafreeze.dsp
!ELSEIF "$(CFG)" == "app_wxluafreeze - Win32 Debug Multilib"
# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1
...
# ADD BASE LINK32 /NODEFAULTLIB:msvcrt.lib wxlua_msw28d_wxlua.lib ...
# ADD LINK32 /NODEFAULTLIB:msvcrt.lib wxlua_msw28d_wxlua.lib ...
I would guess that the reason why we need to do this (wxWidgets
samples do not) is that modules_mod_lua.dsp generates a non-debug
lua5.1.lib for the "debug" setting and MSVC gets confused and ignores
the fact that we've set "Use_Debug_Libraries 1" and links to the
non-debug msvcrt lib? When I change the lua5.1.lib to be debug by hand
I no longer get the 4098 warning and the program doesn't crash, so I
think my theory is correct.
!ELSEIF "$(CFG)" == "mod_lua - Win32 Debug Multilib"
# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1 << change from 0
...
Change /MD to /MDd below
# ADD BASE CPP /nologo /FD /MDd /W1 /GR /EHsc /D "WIN32" /D "_LIB" /c
# ADD CPP /nologo /FD /MDd /W1 /GR /EHsc /D "WIN32" /D "_LIB" /c
===============
Francesco, what do you think about this and which way makes more
sense, add NODEFAULTLIB or change lua5.1.lib to be debug as well?
Regards,
 John Labenski

I've found out that you cannot have static libraries depend on each
other in the *.dsw workspace files for MSVC 6. Apparently only apps
can depend on libraries. MSVC 6 does something strange when you have
static libs depend on each other and warns you that symbols in a
"dependent" static lib are multiply defined even though static libs
are not linked together when built, but later when an app is created.
What this means is that the hundreds of LNK4006 warnings are now gone.
Fixed in CVS.
Regards,
 John Labenski

On 4/15/07, Duncan Cross <dun...@gm...> wrote:
> Thanks, I'll try that. I notice though from that doc page that just
> above the class definition there's this:
>
> %if wxLUA_USE_wxMediaCtrl & wxUSE_MEDIACTRL
>
> ...are these settings all "true" by default in the binary
> distribution, or do you have to "activate" any of them in some way
> first?
Humm, it's currently not compiled in because we have to link to the
media ctrl lib.
http://wxlua.cvs.sourceforge.net/wxlua/wxLua/modules/wxbind/setup/wxluasetup.h?view=markup
I think we should change this to have wxMediaCtrl by default since
it's pretty small. It's hopefully just a matter of adding the lib to
the bakefiles (build file generator) and recreating them. I've changed
it in bakefiles/wxluabase.bkl, but I don't know what version of
bakefile to use to regenerate the build files.
-John Labenski
> On 4/15/07, John Labenski <jla...@gm...> wrote:
> > On 4/15/07, Duncan Cross <dun...@gm...> wrote:
> > > Hello,
> > >
> > > I've only just started looking at wxLua, I've been learning about Lua
> > > for a couple of months but wxWidgets is entirely new to me. It's very
> > > impressive how well everything seems to work.
> >
> > Thanks.
> >
> > > I have a question though. What is the minimum I need to do in order to
> > > get wxMediaCtrl to be available in wxLua (specifically for code
> > > written in the wxLuaEditor IDE, on MSW)? Unless I'm doing something
> > > stupid it seems to simply be absent from the wx table. Is it somehow
> > > incompatible with the Lua layer?
> >
> > I don't remember if it is part of the last binary distribution, but it
> > is currently wrapped. See this doc for all the classes that are
> > wrapped.
> > http://wxlua.sourceforge.net/docs/wxluaref.html#wxMediaCtrl
> >
> > If you are able to compile wxLua you can download one of the snapshots
> > and compile that. We should do another binary release when I/we get
> > some time.
> >
> > Regards,
> > John Labenski
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > wxlua-users mailing list
> > wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Thanks, I'll try that. I notice though from that doc page that just
above the class definition there's this:
 %if wxLUA_USE_wxMediaCtrl & wxUSE_MEDIACTRL
...are these settings all "true" by default in the binary
distribution, or do you have to "activate" any of them in some way
first?
On 4/15/07, John Labenski <jla...@gm...> wrote:
> On 4/15/07, Duncan Cross <dun...@gm...> wrote:
> > Hello,
> >
> > I've only just started looking at wxLua, I've been learning about Lua
> > for a couple of months but wxWidgets is entirely new to me. It's very
> > impressive how well everything seems to work.
>
> Thanks.
>
> > I have a question though. What is the minimum I need to do in order to
> > get wxMediaCtrl to be available in wxLua (specifically for code
> > written in the wxLuaEditor IDE, on MSW)? Unless I'm doing something
> > stupid it seems to simply be absent from the wx table. Is it somehow
> > incompatible with the Lua layer?
>
> I don't remember if it is part of the last binary distribution, but it
> is currently wrapped. See this doc for all the classes that are
> wrapped.
> http://wxlua.sourceforge.net/docs/wxluaref.html#wxMediaCtrl
>
> If you are able to compile wxLua you can download one of the snapshots
> and compile that. We should do another binary release when I/we get
> some time.
>
> Regards,
> John Labenski
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

On 4/15/07, Duncan Cross <dun...@gm...> wrote:
> Hello,
>
> I've only just started looking at wxLua, I've been learning about Lua
> for a couple of months but wxWidgets is entirely new to me. It's very
> impressive how well everything seems to work.
Thanks.
> I have a question though. What is the minimum I need to do in order to
> get wxMediaCtrl to be available in wxLua (specifically for code
> written in the wxLuaEditor IDE, on MSW)? Unless I'm doing something
> stupid it seems to simply be absent from the wx table. Is it somehow
> incompatible with the Lua layer?
I don't remember if it is part of the last binary distribution, but it
is currently wrapped. See this doc for all the classes that are
wrapped.
http://wxlua.sourceforge.net/docs/wxluaref.html#wxMediaCtrl
If you are able to compile wxLua you can download one of the snapshots
and compile that. We should do another binary release when I/we get
some time.
Regards,
 John Labenski