wxlua-users Mailing List for wxLua

Hi,

John Labenski yazmış:
> 2008/1/30 Hakkı Doğusan <hd...@do...>:
>> Hi,
>>
>>[snip]
> 
>> You may get it here:
>> http://www.dynaset.org/dogusanh/download/wxLuaGridTableBase.zip
> 
> Thanks, added to CVS. I've also tried to make sure that all wxGrid
> objects created will be properly garbage collected.
> 

Thanks.

ps. In binding.html there is a "Binding C++ Virtual Functions" section. 
There it explained in detail what is going on for virtual functions; 
but, I think, how to implement those bindings is missing. In other 
words, it is not explained for idiots, like me :) Could you add some doc 
to explain how to generate binding for an artificial ABC C++ class, in 
steps? I masquared(spell?) wxLuaPrintout and wxArtProvider bindings to 
write wxLuaGridTableBase. As you can guess, it took too much jumping in 
code :)


> Regards,
>     John


--
Regards,
Hakki Dogusan

On Jan 30, 2008 6:06 AM,  <Obe...@ix...> wrote:
> Hi,
>
> I'm trying to get a simple wxLua Drag & Drop example
> (D&D of items between two ListCtrls or a ListCtrl and a TreeCtrl)
> to run currently without success.
> In the documentation the wxDropSource class is marked
> with the comment "// FIXME implement virtual"
> and the DoDragDrop() function is not wrapped (commented out): //virtual
> wxDragResult DoDragDrop(int flags = wxDrag_CopyOnly) Now my questions:
> Does this mean D&D is currently not supported by wxLua ? Has someone
> else experience regarding Drag & Drop in wxLua ? Regards
>

Right, it is not implemented yet. I will try to add it in the next few days.

Regards,
    John

MjAwOC8xLzMwIEhha2v9IERv8HVzYW4gPGhkQGRvZ3VzYW4ubmV0PjoKPiBIaSwKPgo+IEkgZm91
bmQgdGhpcyBidWcgd2hpbGUgd29ya2luZyBvbiB3eEdyaWRUYWJsZUJhc2UuCgpXZWxsLCBub3Qg
YSBidWcsIGJ1dCBzaW1wbHkgYSBtaXNzaW5nIGNsYXNzIHRvIGFsbG93IEx1YSBwcm9ncmFtcyB0
bwpvdmVycmlkZSB0aGUgdmlydHVhbCBmdW5jdGlvbnMuCgo+IFlvdSBtYXkgZ2V0IGl0IGhlcmU6
Cj4gaHR0cDovL3d3dy5keW5hc2V0Lm9yZy9kb2d1c2FuaC9kb3dubG9hZC93eEx1YUdyaWRUYWJs
ZUJhc2UuemlwCgpUaGFua3MsIGFkZGVkIHRvIENWUy4gSSd2ZSBhbHNvIHRyaWVkIHRvIG1ha2Ug
c3VyZSB0aGF0IGFsbCB3eEdyaWQKb2JqZWN0cyBjcmVhdGVkIHdpbGwgYmUgcHJvcGVybHkgZ2Fy
YmFnZSBjb2xsZWN0ZWQuCgpSZWdhcmRzLAogICAgSm9obgo=

Hi,

John Labenski yazmış:
> On Jan 28, 2008 3:55 PM, Hakkı Doğusan <hd...@do...> wrote:
>> Hi,
>>
>> (winxp, CVS updated today)
>> I'm getting some error (image attached) for previously working code:
>>
>> printOut.OnPrintPage = function(printOut, pageNum)
>>    local dc = printOut:GetDC()
>>    ...
>>    return true
>> end
> 
> Thanks, fixed in CVS.
> 

Thanks.

I found this bug while working on wxGridTableBase.

You may get it here:
http://www.dynaset.org/dogusanh/download/wxLuaGridTableBase.zip

- wxlua updated from cvs at 2008-01-30 02:15
- modified files:
     bindings\wxwidgets\wxadv_grid.i
     bindings\wxwidgets\wxadv_override.hpp
     modules\wxbind\include\wxcore_wxlcore.h
     modules\wxbind\src\wxcore_wxlcore.cpp
- added sample (from wx/samples/grid/griddemo.cpp BugsGridTable):
     samples\gridtable.wx.lua


>> (Note: wxMemoryFSHandler is not included in CVS)
> 
> Sorry, I forgot, since I wanted to add all the handlers and not just
> the one. They're all added now in CVS.
> 

Thanks, again.

> Regards,
>     John


--
Regards,
Hakki Dogusan

Hi,

I'm trying to get a simple wxLua Drag & Drop example=20
(D&D of items between two ListCtrls or a ListCtrl and a TreeCtrl)=20
to run currently without success.=20
In the documentation the wxDropSource class is marked=20
with the comment "// FIXME implement virtual"
and the DoDragDrop() function is not wrapped (commented out): //virtual
wxDragResult DoDragDrop(int flags =3D wxDrag_CopyOnly) Now my questions:
Does this mean D&D is currently not supported by wxLua ? Has someone
else experience regarding Drag & Drop in wxLua ? Regards

KlausO

T24gSmFuIDI4LCAyMDA4IDM6NTUgUE0sIEhha2v9IERv8HVzYW4gPGhkQGRvZ3VzYW4ubmV0PiB3
cm90ZToKPiBIaSwKPgo+ICh3aW54cCwgQ1ZTIHVwZGF0ZWQgdG9kYXkpCj4gSSdtIGdldHRpbmcg
c29tZSBlcnJvciAoaW1hZ2UgYXR0YWNoZWQpIGZvciBwcmV2aW91c2x5IHdvcmtpbmcgY29kZToK
Pgo+IHByaW50T3V0Lk9uUHJpbnRQYWdlID0gZnVuY3Rpb24ocHJpbnRPdXQsIHBhZ2VOdW0pCj4g
ICAgbG9jYWwgZGMgPSBwcmludE91dDpHZXREQygpCj4gICAgLi4uCj4gICAgcmV0dXJuIHRydWUK
PiBlbmQKClRoYW5rcywgZml4ZWQgaW4gQ1ZTLgoKPiAoTm90ZTogd3hNZW1vcnlGU0hhbmRsZXIg
aXMgbm90IGluY2x1ZGVkIGluIENWUykKClNvcnJ5LCBJIGZvcmdvdCwgc2luY2UgSSB3YW50ZWQg
dG8gYWRkIGFsbCB0aGUgaGFuZGxlcnMgYW5kIG5vdCBqdXN0CnRoZSBvbmUuIFRoZXkncmUgYWxs
IGFkZGVkIG5vdyBpbiBDVlMuCgpSZWdhcmRzLAogICAgSm9obgo=

Hi,

(winxp, CVS updated today)

I'm getting some error (image attached) for previously working code:


printOut.OnPrintPage = function(printOut, pageNum)
   local dc = printOut:GetDC()
   ...
   return true
end


(Note: wxMemoryFSHandler is not included in CVS)


--
Regards,
Hakki Dogusan

Hi,

John Labenski yazmış:
> 2008/1/21 Ryan Pusztai <rpu...@gm...>:
>> On Jan 21, 2008 5:26 AM, Hakkı Doğusan <hd...@do...> wrote:
>>
>>> I'll experiment with these controls. But maybe some of you already
>>> worked on them. If so, could you share your thoughts/bindings etc.?
>>>
>> I think a binding for wxPropGrid would be good.
> 
> wxWidgets odbc lib is either gone or probably will be in the next
> major wxWidgets release so I wouldn't put any effort into it.
> 

I never used wx's ODBC classes; I'm using SQLite3 (via wxSQLite3) / 
FireBird (via IBPP) databases. I already have -hand written- Lua 
bindings of wxSQLite3 and IBPP. In a recent C++ project, I used 
wxGrid/FireBird (code taken from FlameRobin); I like it. Now I want to 
test/use them with wxLua.

> Extra controls like the wxPropertyGrid would be nice.
> 

I agree. But, it seems nobody has a binding for it.

(Is there any rule about accepting third party code in wxLua? For 
example wxPropertyGrid is not in wx' source tree; if somebody write a 
binding for it, will it find a place in wxLua?)

> Regards,
>     John
> 

--
Regards,
Hakki Dogusan

MjAwOC8xLzIxIFJ5YW4gUHVzenRhaSA8cnB1c3p0YWlAZ21haWwuY29tPjoKPiBPbiBKYW4gMjEs
IDIwMDggNToyNiBBTSwgSGFra/0gRG/wdXNhbiA8aGRAZG9ndXNhbi5uZXQ+IHdyb3RlOgo+Cj4g
PiBJJ2xsIGV4cGVyaW1lbnQgd2l0aCB0aGVzZSBjb250cm9scy4gQnV0IG1heWJlIHNvbWUgb2Yg
eW91IGFscmVhZHkKPiA+IHdvcmtlZCBvbiB0aGVtLiBJZiBzbywgY291bGQgeW91IHNoYXJlIHlv
dXIgdGhvdWdodHMvYmluZGluZ3MgZXRjLj8KPiA+Cj4KPiBJIHRoaW5rIGEgYmluZGluZyBmb3Ig
d3hQcm9wR3JpZCB3b3VsZCBiZSBnb29kLgoKd3hXaWRnZXRzIG9kYmMgbGliIGlzIGVpdGhlciBn
b25lIG9yIHByb2JhYmx5IHdpbGwgYmUgaW4gdGhlIG5leHQKbWFqb3Igd3hXaWRnZXRzIHJlbGVh
c2Ugc28gSSB3b3VsZG4ndCBwdXQgYW55IGVmZm9ydCBpbnRvIGl0LgoKRXh0cmEgY29udHJvbHMg
bGlrZSB0aGUgd3hQcm9wZXJ0eUdyaWQgd291bGQgYmUgbmljZS4KClJlZ2FyZHMsCiAgICBKb2hu
Cg==

On Jan 21, 2008 9:24 AM, Ryan Pusztai <rpu...@gm...> wrote:
>
> On Jan 21, 2008 8:46 AM, Leslie Newell <les...@fm...> wrote:
> > By the way, might
> > it be better to call it wxlua.dll instead of wx.dll?
> >
>
> Well the way that Lua "require()" works would make it so that you need to
> require wxLua and then I think the wx.xxx won't work anymore.

Right, require("wx") looks for the shared library wx.so/dll, a
function called "int luaopen_wx(lua_State *L)" in that library, and
implies that a table named "wx" will have things loaded into it.

It would be nice to call it "wxlua.so/dll" to really ensure
uniqueness, but I think it's ok as is for now.

Regards,
    John

On Jan 20, 2008 11:44 PM, John Labenski <jla...@gm...> wrote:

> It works in Linux. I've found a few problems using MSVC6, but I think
> I'll have them solved tonight.
>
> Use $configure --enable-monolithic-luamodule=yes
>
> For msw makefiles use MONOLITHIC_LUAMODULE=1
>
> For MSVC projects select mod_luamodule_mono


Great! Thanks, I will test it and let you know how it works.
-- 
Regards,
Ryan

On Jan 21, 2008 8:46 AM, Leslie Newell <les...@fm...> wrote:
>
> By the way, might
> it be better to call it wxlua.dll instead of wx.dll?
>

Well the way that Lua "require()" works would make it so that you need to
require wxLua and then I think the wx.xxx won't work anymore.
-- 
Regards,
Ryan

T24gSmFuIDIxLCAyMDA4IDU6MjYgQU0sIEhha2v9IERv8HVzYW4gPGhkQGRvZ3VzYW4ubmV0PiB3
cm90ZToKCj4gSSdsbCBleHBlcmltZW50IHdpdGggdGhlc2UgY29udHJvbHMuIEJ1dCBtYXliZSBz
b21lIG9mIHlvdSBhbHJlYWR5Cj4gd29ya2VkIG9uIHRoZW0uIElmIHNvLCBjb3VsZCB5b3Ugc2hh
cmUgeW91ciB0aG91Z2h0cy9iaW5kaW5ncyBldGMuPwo+CgpJIHRoaW5rIGEgYmluZGluZyBmb3Ig
d3hQcm9wR3JpZCB3b3VsZCBiZSBnb29kLgotLSAKUmVnYXJkcywKUnlhbgo=

Hi John,

msw makefile seemed to work for me. Interestingly it also produced the 
individual dlls as well. This is not a problem for me. By the way, might 
it be better to call it wxlua.dll instead of wx.dll?

Thanks,
Les

John Labenski wrote:
>
> It works in Linux. I've found a few problems using MSVC6, but I think
> I'll have them solved tonight.
>
> Use $configure --enable-monolithic-luamodule=yes
>
> For msw makefiles use MONOLITHIC_LUAMODULE=1
>
> For MSVC projects select mod_luamodule_mono
>
> Regards,
>     John
>   

Hi,


I'll experiment with these controls. But maybe some of you already 
worked on them. If so, could you share your thoughts/bindings etc.?


--
Regards,
Hakki Dogusan

Hi,

John Labenski yazmış:
> On Jan 20, 2008 7:17 PM, Hakkı Doğusan <hd...@do...> wrote:
>> Hi,
>>
>> Current cvs includes image sample's image files, but lua file is missing :)
>>
> 
> Oops, thanks for providing it.
> 

Your welcome.

> Regards,
>     John
> 
> By the way, what do you think about the wxBitmap constructor for bits?
> I think I'm going to add a table override instead of just taking a
> string since I imagine that people would only use it as a replacement
> for #including an xbm.
> 

Fine, it'll remove array-to-string process from user code.

> --#include "smile.xbm"
> local smile_width = 32
> local smile_height = 32
> local smile_bits = {
>[snip bits]
}
> 
> local C = string.char
> for i = 1, #smile_bits do
>     smile_bits[i] = C(smile_bits[i]) -- turn into ASCII chars
> end
> smile_bits = table.concat(smile_bits) -- turn into a string
> 
> ...
> 
>     this.my_smile_xbm = wx.wxBitmap( smile_bits, smile_width,
>                                  smile_height, 1 )

--
Regards,
Hakki Dogusan

On Jan 20, 2008 11:02 PM, Ryan Pusztai <rpu...@gm...> wrote:
> Is the monolithic build ready? If so, can I get a few details on how I can
> build the monolithic library from the makefiles, both in Windows and Linux?

It works in Linux. I've found a few problems using MSVC6, but I think
I'll have them solved tonight.

Use $configure --enable-monolithic-luamodule=yes

For msw makefiles use MONOLITHIC_LUAMODULE=1

For MSVC projects select mod_luamodule_mono

Regards,
    John

Is the monolithic build ready? If so, can I get a few details on how I can
build the monolithic library from the makefiles, both in Windows and Linux?
Thanks.
-- 
Regards,
Ryan

T24gSmFuIDIwLCAyMDA4IDc6MTcgUE0sIEhha2v9IERv8HVzYW4gPGhkQGRvZ3VzYW4ubmV0PiB3
cm90ZToKPiBIaSwKPgo+IEN1cnJlbnQgY3ZzIGluY2x1ZGVzIGltYWdlIHNhbXBsZSdzIGltYWdl
IGZpbGVzLCBidXQgbHVhIGZpbGUgaXMgbWlzc2luZyA6KQo+CgpPb3BzLCB0aGFua3MgZm9yIHBy
b3ZpZGluZyBpdC4KClJlZ2FyZHMsCiAgICBKb2huCgpCeSB0aGUgd2F5LCB3aGF0IGRvIHlvdSB0
aGluayBhYm91dCB0aGUgd3hCaXRtYXAgY29uc3RydWN0b3IgZm9yIGJpdHM/CkkgdGhpbmsgSSdt
IGdvaW5nIHRvIGFkZCBhIHRhYmxlIG92ZXJyaWRlIGluc3RlYWQgb2YganVzdCB0YWtpbmcgYQpz
dHJpbmcgc2luY2UgSSBpbWFnaW5lIHRoYXQgcGVvcGxlIHdvdWxkIG9ubHkgdXNlIGl0IGFzIGEg
cmVwbGFjZW1lbnQKZm9yICNpbmNsdWRpbmcgYW4geGJtLgoKLS0jaW5jbHVkZSAic21pbGUueGJt
Igpsb2NhbCBzbWlsZV93aWR0aCA9IDMyCmxvY2FsIHNtaWxlX2hlaWdodCA9IDMyCmxvY2FsIHNt
aWxlX2JpdHMgPSB7CiAgIDB4MDAsIDB4MDAsIDB4MDAsIDB4MDAsIDB4MDAsIDB4ZTAsIDB4MDMs
IDB4MDAsIDB4MDAsIDB4MWMsIDB4MWMsIDB4MDAsCiAgIDB4MDAsIDB4MDMsIDB4NjAsIDB4MDAs
IDB4ODAsIDB4MDAsIDB4ODAsIDB4MDAsIDB4NjAsIDB4MDAsIDB4MDAsIDB4MDMsCiAgIDB4MjAs
IDB4MDAsIDB4MDAsIDB4MDQsIDB4MTAsIDB4MDgsIDB4MDgsIDB4MDQsIDB4MDgsIDB4MTQsIDB4
MTQsIDB4MDgsCiAgIDB4MDgsIDB4MjIsIDB4MjIsIDB4MTAsIDB4MDQsIDB4MDEsIDB4NDAsIDB4
MTAsIDB4MDQsIDB4MDgsIDB4MDgsIDB4MTAsCiAgIDB4MDQsIDB4MDgsIDB4MDgsIDB4MTAsIDB4
MDIsIDB4MDAsIDB4MDAsIDB4MjAsIDB4MDIsIDB4MDAsIDB4MDAsIDB4MjAsCiAgIDB4MDIsIDB4
MDAsIDB4MDAsIDB4MjAsIDB4MDIsIDB4MDAsIDB4MDAsIDB4MjAsIDB4MDIsIDB4MDIsIDB4MjAs
IDB4MjAsCiAgIDB4MDQsIDB4MGUsIDB4MzgsIDB4MTAsIDB4MDQsIDB4M2UsIDB4M2UsIDB4MTAs
IDB4MDQsIDB4ZjQsIDB4MWIsIDB4MTAsCiAgIDB4MDgsIDB4ZDgsIDB4MGEsIDB4MTAsIDB4MDgs
IDB4YjAsIDB4MDcsIDB4MDgsIDB4MTAsIDB4YzAsIDB4MDEsIDB4MDQsCiAgIDB4MjAsIDB4MDAs
IDB4MDAsIDB4MDQsIDB4NjAsIDB4MDAsIDB4MDAsIDB4MDMsIDB4ODAsIDB4MDAsIDB4ODAsIDB4
MDAsCiAgIDB4MDAsIDB4MDMsIDB4NjAsIDB4MDAsIDB4MDAsIDB4MWMsIDB4MWMsIDB4MDAsIDB4
MDAsIDB4ZTAsIDB4MDMsIDB4MDAsCiAgIDB4MDAsIDB4MDAsIDB4MDAsIDB4MDAsIDB4MDAsIDB4
MDAsIDB4MDAsIDB4MDAgfQoKbG9jYWwgQyA9IHN0cmluZy5jaGFyCmZvciBpID0gMSwgI3NtaWxl
X2JpdHMgZG8KICAgIHNtaWxlX2JpdHNbaV0gPSBDKHNtaWxlX2JpdHNbaV0pIC0tIHR1cm4gaW50
byBBU0NJSSBjaGFycwplbmQKc21pbGVfYml0cyA9IHRhYmxlLmNvbmNhdChzbWlsZV9iaXRzKSAt
LSB0dXJuIGludG8gYSBzdHJpbmcKCi4uLgoKICAgIHRoaXMubXlfc21pbGVfeGJtID0gd3gud3hC
aXRtYXAoIHNtaWxlX2JpdHMsIHNtaWxlX3dpZHRoLAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBzbWlsZV9oZWlnaHQsIDEgKQo=

Hi,

Current cvs includes image sample's image files, but lua file is missing :)


--
Regards,
Hakki Dogusan

On Jan 20, 2008 5:09 AM, Anders F Bj=F6rklund <af...@al...> wrote:
> Sebastian Ahlman wrote:
>
> > I was recently asked to create a small OSX app and I thought about
> > creating it in wxLua since I have succesfully made an app using it
> > before. When can I expect a new release for the Mac? Also, why is the
> > newest version on the site not available for the Mac? Are the updates
> > irrelevant on OSX?
>
> Mac OS X in about the same time as it is for the other platforms.
> (both as a standalone download, and also available through MacPorts)
>
> Not sure when that is, though. :-) Seems to work alright from CVS.

One more internal change. The wxLua types are integers and their
values are currently generated when the wxLuaState pushes the bindings
into Lua. This needs to be changed so that they are generated at the
program's initialization so people can initialize as many or as few of
the bindings as they like on a per-wxLuaState basis.

> > Anything else I should know about when planning the app (that will
> > probably be used for mission critical tasks for a few years to come)?.
>
> There's a few things that need to be documented and implemented,
> with respect to the example IDE program and the standalone runtime
> (wxLua and wxLuaFreeze) so that you can e.g. drag-and-drop files
> to the program, and to make it easier to create wxLua applications.

I saw on wx-dev about this for wxApp, I guess we need to implement it.
I'll give it a shot.

    // in response of an open-document apple event
    virtual void         MacOpenFile(const wxString &fileName) ;

Regards,
     John

John Labenski ha scritto:
> On Jan 20, 2008 5:51 AM, Francesco Montorsi <f18...@ya...> wrote:
>> Hi,
>>
>> Francesco Montorsi ha scritto:
>>> Besides the various bugfixes and the fact we can now use a vanilla
>>> bakefile version (instead of the patched one), v0.2.3 also supports the
>>> msvs2003prj format, i.e. MSVC IDE project files for vc++ 7.1.
>>>
>>> Is anyone using msvc 7.1? If so, we could add some "msvc7" folders next
>>> to the "msvc6" and "msvc8" ones...
>> In fact, I think that since also wx has partially dropped support to
>> msvc6, we could remove msvc6 folders completely in favour of msvc7
>> ones... what do you think?
>>
>> Or maybe we could do a last release with msvc6 support (maybe next to
>> msvc7 one) and then remove it from HEAD/TRUNK...
> 
> I still use MSVC6 and like it, it's the only compiler in MSWin that I
> use. The last I heard was that MSVC6 in wxWidgets was still supported
> since Julian likes it too. I'd like to keep the MSVC6 build files
> until wxWidgets removes them.
ok

> Isn't MSVC 7.1 (aka. 2003) is the last MSVC that doesn't require the
> .NET runtime (the massive 50-100Mb lib whatever it's called), so it's
> nice. Isn't 7.1 a nmake.exe only version? If yes, can't they just use
> the MSVC6 makefiles?
as other replied, MSVC 7.1 is just like v6 or v8; it's a full IDE with 
full nmake.exe; BTW it's also my favourite MSVC version: it has a modern 
compiler but does not have all the "rings & bells" (e.g. lots of .net 
stuff related) of MSVC v8, which is also slower, a bit more bloated and 
lacks the plaform SDK.


> ===================================
> 
> Francesco, can you check the line endings of the makefile.vc files in
> Linux? Mine are CRLF!
mine too

> Is this a new change for bakefile?
ach! sorry I completely forgot. This indeed is a change in behaviour of 
bakefile 0.2.3 and well, the --eol option was added by a patch done, 
well, by me :)

I forgot it because that patch was applied lots of time ago...

> I see that we
> can use "bakefile --eol=native"
indeed now bakefile runs with --eol=format which is ok for SVN, not for CVS.

>, but this option doesn't exist for
> bakefile_gen.
well, it doesn't need to be supported by bakefile_gen. I.e. to add 
--eol=native string to all calls to bakefile done internally by 
bakefile_gen, we just need
     <add-flags>--eol=native</add-flags>
in Bakefiles.bkgen.

I've added it, rebaked and committed everything.

> I think this is why people are having problems in the
> makefile.vc thread.
sure; sorry for not connecting the two things (--eol option addition and 
the thread) before... I just though: it's useless to try to fix EOL 
problems if we have already decided to switch to SVN since SVN allows to 
fix these problems once and for all just setting svn:eol-style property.

Francesco

On Jan 20, 2008 9:45 PM, John Labenski <jla...@gm...> wrote:
>
> As an aside, have you noticed that Windows XP becomes very sluggish
> after installing either of these compilers? I have usually installed
> 2005 on my systems and soon after have noticed that the start menu,
> redrawing of the desktop, and explorer have long delays in them. I
> can't find anything on the web about this, but I'm suspicious. Maybe
> it bloats the registry?
>

I cannot really comment on this, My problems have mostly been
related to how badly XP seems to behave when there is a CPU hog process
running and the processor does not have multi-core-or-multi-thread...
I have not noticed special problems with the compilers.

> > One related issue: Visual C++ 2005 express edition + the free platform SDK
> > kit which I have installed with it do not contain the odbc32 library which is
> > in apps/msw/makefile.vc.  I removed the library from the makefile, and noticed
> > that wxLua compiled fine without it.
>
> How do you compile wxWidgets? You use 2.8.7? I see that all wxWidget's
> *.dsp files and makefile.vc link to it.
>

Odd, quickly checking at the makefiles... It looks like that the library is not
needed in wxWidgets (library) compilation, when the wxWidgets  is not compiled
as a shared library.  So I have not needed to do anything because I use the
static library version.

  Eero

On Jan 20, 2008 12:39 PM, Eero Pajarre <epa...@gm...> wrote:
> > Isn't MSVC 7.1 (aka. 2003) is the last MSVC that doesn't require the
> > .NET runtime (the massive 50-100Mb lib whatever it's called), so it's
> > nice. Isn't 7.1 a nmake.exe only version? If yes, can't they just use
> > the MSVC6 makefiles?
> >
>
> I don't know what the compilers them self require, but the  2005 version
> (and most probably 2008 version) can produce real executables,
> which are not .net based.

Right, sorry, as you say the platform SDK.

> Also both 2005 and 2008 version are available for free (as beer), and these
> are "full versions" in that sense that normal optimization etc features are
> supported.

As an aside, have you noticed that Windows XP becomes very sluggish
after installing either of these compilers? I have usually installed
2005 on my systems and soon after have noticed that the start menu,
redrawing of the desktop, and explorer have long delays in them. I
can't find anything on the web about this, but I'm suspicious. Maybe
it bloats the registry?

> One related issue: Visual C++ 2005 express edition + the free platform SDK
> kit which I have installed with it do not contain the odbc32 library which is
> in apps/msw/makefile.vc.  I removed the library from the makefile, and noticed
> that wxLua compiled fine without it.

How do you compile wxWidgets? You use 2.8.7? I see that all wxWidget's
*.dsp files and makefile.vc link to it.

Regards,
    John

> Isn't MSVC 7.1 (aka. 2003) is the last MSVC that doesn't require the
> .NET runtime (the massive 50-100Mb lib whatever it's called), so it's
> nice. Isn't 7.1 a nmake.exe only version? If yes, can't they just use
> the MSVC6 makefiles?
>

I don't know what the compilers them self require, but the  2005 version
(and most probably 2008 version) can produce real executables,
which are not .net based.

Also both 2005 and 2008 version are available for free (as beer), and these
are "full versions" in that sense that normal optimization etc features are
supported.

Both of the compilers can read the old project files (but  like the
2003 version) they
will convert it to their own version. Both also include nmake for command line
compilation. I have used the 2005 nmake compilation with wxLua.

One related issue: Visual C++ 2005 express edition + the free platform SDK
kit which I have installed with it do not contain the odbc32 library which is
in apps/msw/makefile.vc.  I removed the library from the makefile, and noticed
that wxLua compiled fine without it.

 Eero