wxlua-users — wxLua list for users and developers

[Wxlua-users] wxLua website (was Re: wxlua linux)

[Francesco M. <f18...@ya...>]

Hi,

k. holwerda ha scritto:
> Forget about the old site.

I've found that searching for wxLua in google gives this link:
       A) http://www.luascript.thersgb.net
and the site at:
       B) http://wxlua.sf.net

is not as good as the A) link :)

We could ask to the owner of the A) link, to let us copy the contents of 
the website on B) and then setup a redirection from A) to B).

IMHO the current situation is confusing. There should be a single 
website for each single project (mirroring it would only generate synch 
problems IMO).

This is not a primary issue, though.
Unless until we don't have wxLua 2.6.2.1 ready :))

Francesco

[Wxlua-users] wxLua and wxWidgets versions (was Re: target names)

[Francesco M. <f18...@ya...>]

Hi,

k. holwerda ha scritto:
> 
> 
> Francesco Montorsi wrote:
> 
>> Hi,
>>
>>
>>      libwxlua_[gtk2|x11|msw|...][u][d]_lua-[wxversion].so.0
>>      libwxlua_[gtk2|x11|msw|...][u][d]_lualib-[wxversion].so.0
>>      libwxlua_[gtk2|x11|msw|...][u][d]_wxbind-[wxversion].so.0
>>      libwxlua_[gtk2|x11|msw|...][u][d]_wxlua-[wxversion].so.0
>>      libwxlua_[gtk2|x11|msw|...][u][d]_wxluadebug-[wxversion].so.0
>>      libwxlua_[gtk2|x11|msw|...][u][d]_wxluasocket-[wxversion].so.0
Just a few things which came up to my mind while updating bakefiles:
1) on win32 it's best not to use a version in the libname with dots 
(instead of 2.6, we should use 26); furthermore, we can even choose to 
use the same wx library convention:

            wxmsw[wxversion without dots][u][d]_[libname].lib

  So, what do you propose? I think that while on linux we can adopt a 
more complex library naming (like 
libwxlua_[gtk2|x11|msw|...][u][d]_lua-[wxversion].so.0) since the user 
will probably use `pkg-config wxlua --libs` to get libname, on win32 we 
should keep the library name shorter as wxWidgets does.
Thus I suggest to stick with wx rules for both linux and win32 libnames.



2) We are going to put wxversion numbers somewhere in library names  in 
any case. However I'd like to discuss a couple of things about version.

I see wxPython works this way: for wx2.6.2 there is wxPython2.6.2.1, 
wxPython2.6.1.2, etc...
This is probably the best thing to do as it will be simpler for users to 
  understand which release of wxPython targets which release of 
wxWidgets but still lets wxPython developers to make other releases 
still targeted  to wx 2.6.2 using the fourth digit.

Do you agree to use this versioning rule ?

AFAIK the only files containing wxLua version numbers should be:
1) build/bakefiles/wxluabase.bkl
2) build/autoconf/configure.ac

If we decide to use a wxPython-like versioning, then we can store a 
single version number in these files (the fourth number).

In any case we would still use only wx major and minor version digits in 
libnames, unless someone has other ideas....


Francesco

[Wxlua-users] Re: wxlua linux

[k. h. <kla...@nl...>]

Hi,

WxLua is now on sourceforge,

cvs.sourceforge.net:/cvsroot/wxlua

Forget about the old site.
We just recently started to get it to work on linux, almost finished.

The makefiles are much improved and VC project files are available.
All generated via bakefile, used in wxWidgets too.

You compile and install wxWidgets 2.6.2 and after that wxLua.
In case of problems, the mailing list  of wxLua is at:

wxl...@li...

regards,

Klaas

ro...@co... wrote:

> Has anyone got a copy of the wxLua binary for Linux tarball? I'm about 
> to go completely bald pulling my hair out over the stupid broken link 
> on the wxlua website. It seems only the Windows .zip files are 
> available - the .tar.gz have vanished. I can't even find them in 
> archive.org!!!
>
> Tried to  compile the windows source (I'm assuming it's the same as 
> the tared source) but I've run into several weird compiler errors. I 
> just want the dratted binary for crying out loud!
>
> So... Um... Help! Please... :-(
>
>  Thanx! :-D
>
>  
>
> - Rodney 
>
>

-- 
Unclassified

Re: [Wxlua-users] Re: wxLua on win32

[k. h. <kla...@nl...>]

k. holwerda wrote:

>
>
> Francesco Montorsi wrote:
>
>
>> -> fixed wxLua.dsw
>
app_wxlua complains in batch build that it can not find wxluasocket.lib, 
but the second time it is oke,
I think this is a dependency problem.

--------------------Configuration: app_wxlua - Win32 
Debug--------------------
Compiling resources...
Compiling...
lconsole.cpp
wxlua.cpp
Generating Code...
Linking...
LINK : fatal error LNK1104: cannot open file "wxluasocket.lib"
Error executing link.exe.


Can the default configuration be set to debug? Or is this not best?



After setting WXSTEDIT correctly, i still get, and doing:

// If you get an error on this line, maybe you forgot to copy
//   include/wx/stedit/setup0.h to include/wx/stedit/setup.h ?

I get this:

--------------------Configuration: app_wxluaedit - Win32 
Debug--------------------
Linking...
LINK : fatal error LNK1104: cannot open file "wxmsw26d_stedit.lib"
Error executing link.exe.

wxluaedit.exe - 1 error(s), 0 warning(s)

BTW what did i see when compiling wxstedit, yecka there it is again ;-)

--------------------Configuration: wxstedit - Win32 
Debug--------------------
Compiling resources...
Compiling...
wxstedit.cpp
Linking...
LINK : warning LNK4098: defaultlib "MSVCRT" conflicts with use of other 
libs; use /NODEFAULTLIB:library

wxstedit.exe - 0 error(s), 1 warning(s)


My stedit produces libraries steditd.lib and stedit.lib, do i need an 
update there?
Anyway i renamed them, but same problem,

I think ( i am sure )  you need to add:

/libpath:"$(WXSTEDIT)\lib"


Oke running app_wxluaedit gives me ( this must be because of the swicth 
problem again ):

NTDLL! 77f767cd()
NTDLL! 77f6a6a0()
KERNEL32! 77e6c7c4()
_CrtIsValidHeapPointer(const void * 0x01222d08) line 1697
_free_dbg_lk(void * 0x01222d08, int 1) line 1044 + 9 bytes
_free_dbg(void * 0x01222d08, int 1) line 1001 + 13 bytes
free(void * 0x01222d08) line 956 + 11 bytes
wxListKey::~wxListKey() line 379 + 15 bytes
wxListBase::Append(const char * 0x00b5089c, void * 0x00c47760 class 
wxClassInfo wxLuaShell::ms_classInfo) line 273
wxObjectList::Append(const char * 0x00b5089c, void * 0x00c47760 class 
wxClassInfo wxLuaShell::ms_classInfo) line 1122 + 30 bytes
wxHashTable::Put(const char * 0x00b5089c, wxObject * 0x00c47760 class 
wxClassInfo wxLuaShell::ms_classInfo) line 485
wxClassInfo::Register() line 245
wxClassInfo::wxClassInfo(const char * 0x00b5089c, const wxClassInfo * 
0x00c483c0 class wxClassInfo wxSTEditorShell::ms_classInfo, const 
wxClassInfo * 0x00000000, int 472, wxObject * (void)* 0x00000000) line 77
$E391() line 48 + 32 bytes
$E395() + 8 bytes
_initterm(void (void)* * 0x00b4d10c $S396, void (void)* * 0x00b4e8a8 
___xc_z) line 525
WinMainCRTStartup() line 274 + 15 bytes
KERNEL32! 77e8141a()


It looks like the problem is in wxstedit all the time ( which i am using 
in wxArt2D too ).

Hope you can fix this.

app_wxlua complains about wxStryledTextCtrl being nill, which is a lua 
problem i think.

Coming closer to perfect ;-)

regards,

Klaas




-- 
Unclassified

Re: [Wxlua-users] Re: target names

[k. h. <kla...@nl...>]

Francesco Montorsi wrote:

> Hi,
>
>
>      libwxlua_[gtk2|x11|msw|...][u][d]_lua-[wxversion].so.0
>      libwxlua_[gtk2|x11|msw|...][u][d]_lualib-[wxversion].so.0
>      libwxlua_[gtk2|x11|msw|...][u][d]_wxbind-[wxversion].so.0
>      libwxlua_[gtk2|x11|msw|...][u][d]_wxlua-[wxversion].so.0
>      libwxlua_[gtk2|x11|msw|...][u][d]_wxluadebug-[wxversion].so.0
>      libwxlua_[gtk2|x11|msw|...][u][d]_wxluasocket-[wxversion].so.0
>
> Do you agree ?
>
I do agree!

Klaas

-- 
Unclassified

Re: [Wxlua-users] Re: wxLua on win32

[k. h. <kla...@nl...>]

Francesco Montorsi wrote:

> -> wxLua's configure can be called from any directory
>    (running wxLua/mybuild/../configure && make && make install now works)

So you mean building outside wxLua too, and all stuff going there?
That is really cool!

> -> fixed wxLua.dsw

Oke thanks,

Will test now.

Klaas


-- 
Unclassified

Re: [Wxlua-users] Remaining problems on Linux (Re: wxLua on Linux)

[k. h. <kla...@nl...>]

Will test linux this evening, i am  trying to set op Suse10.1 ( really 
nice ) currently.
So hope to give you some feedback, on the linux compile soon.

Klaas

Francesco Montorsi wrote:

> Hi,
>
> John Labenski ha scritto:
>
>> On 1/23/06, Francesco Montorsi <f18...@ya...> wrote:
>>
>>>>>> ./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is
>>>>>> not defined
>>>>>
>> Ok, I've added a new setting in wx.rules where you can add any
>> additional code for the binding header. There is where I've placed
>>
>> #ifndef wxUSE_WAVE
>> #define wxUSE_WAVE 0
>> #endif
>>
>> so that ti should work anywhere. It's a little bit of a hack, but I
>> think this is all we can do to maintain backwards compatibility.
>
> I confirm that wxUSE_WAVE warning is disappeared.
>
> Still we have at least the following problems:
>
> 1) STC (more generically CONTRIB) problem
>
> 2) wxLUA_USE_wxCriticalSectionLocker is not defined - maybe it should 
> be added to wxluasetup.h
>
> 3) wxLua application needs wxStyledTextCtrl wrapper and an error 
> should be given when it's not available instead of just failing it at 
> runtime (IMO)
>
> 4) currently doing a thing like:
>      mkdir mybuild && cd mybuild && ../configure && make
>    doesn't work. I'm going to fix this tomorrow.
>
> 5) change the target names to avoid clashes with system installations 
> of LUA.
>
>
> For more info about #1 and #3 please look at my other mails in this 
> same thread. For #5 see 'target names' thread.
>

-- 
Unclassified

[Wxlua-users] Re: wxLua on win32

[Francesco M. <f18...@ya...>]

Hi,
    just committed the following build fixes:
-> wx default version is now 2.6
-> DSW/DSP files use CRLF EOL
-> wxLua's configure can be called from any directory
    (running wxLua/mybuild/../configure && make && make install now works)
-> fixed wxLua.dsw

Francesco


Francesco Montorsi ha scritto:
> Hi,
> 
> k. holwerda ha scritto:
> 
>> Hi,
>>
>> John Labenski wrote:
>>
>>>> So leafs the not found target.
>>>>
>>>> I see in the modules a split in sourse and headers, nice!
>>>> Can it be made non capital in all cases?
>>>>
>>>> In apps.dsw, i get can not open wxmsw27d_xrc.lib, indeed that i don't
>>>> have ;-)
>>>> I have wxmsw26d_xrc.lib, how come?
>>>>   
>>>
>>>
>>>
>>> The last update using bakefile has changed from 26 to 27. I use
>>> wxWidgets CVS head so this is not a problem, but we should revert to
>>> 26 since that is the stable brach of wxWidgets.
> 
> sure; that's my fault.
> I'm going to set it in wxLua bakefiles so that won't be a problem anymore.
> 
> 
>>>  
>>>
>> I am suprized why it  is not recognized automatically using WXWIN?
> 
> WXWIN only gives info about location of wxWidgets, not its version.
> 
> 
>>>> How does one deal with stedit in the second target? Maybe that 
>>>> should go
>>>> into install.html too.
>>>>   
>>>
>>>
>>>
>>> What second target?
>>>  
>>>
>> wxluaedit uses stedit, so the second target in that apps.dsw
> 
> if I understand it correctly (please remember that it's quite a bit of 
> time I'm not using MSVC anymore and I don't have a fresh idea of how 
> wxLua project files look and how many are the targets and how they are 
> exactly named :)), this is the same problem I have on linux :)
> 
> See problem #1 in my "Remaining problems" mails
> 
> 
>>>>> Trying to test it.
>>>>>
>>>>> In the project file wxLua.dsw, VC6 could not find target app_wxLua, it
>>>>> seems to search for
>>>>> wxLua/apps/build/msw/apps.dsp.
>>>>> And indeed i could not find it, although there is apps.dsw.
>>>>>
>>>>> Can you fix that?
>>>>>     
>>>
>>>
>>>
>>> apps.dsp has been removed, do another checkout.
> 
> anyway I updated apps.dsw to match the new DSP names
> 
> 
>> And it is all LF again, so no project file works anymore.
> 
> if you are checking out from a win32 box and DSP files were added to CVS 
> repository as text files, this should never happen (CVS should check 
> them out using CRLF). Maybe they were added as binary.
> In frm-bakefile 0.2.0 I have added a --crlf=(native|dos|mac|unix) option 
> which I could use to tell bakefile_gen to generate DSW/DSP files always 
> with dos EOL...
> 
> I'm going to do that ASAP.
> 
> 
>>>>> Is there already a cleanall /deep ?  I see that things get mixed up in
>>>>> project files, so a real good/all clean like in wxArt2D  is needed i
>>>>> think.
> 
> I'll test wxLua project files as soon as linux problems are solved...
> 
> Francesco
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

[Wxlua-users] Re: wxLua on win32

[Francesco M. <f18...@ya...>]

Hi,

k. holwerda ha scritto:
> Hi,
> 
> John Labenski wrote:
> 
>>> So leafs the not found target.
>>>
>>> I see in the modules a split in sourse and headers, nice!
>>> Can it be made non capital in all cases?
>>>
>>> In apps.dsw, i get can not open wxmsw27d_xrc.lib, indeed that i don't
>>> have ;-)
>>> I have wxmsw26d_xrc.lib, how come?
>>>   
>>
>>
>> The last update using bakefile has changed from 26 to 27. I use
>> wxWidgets CVS head so this is not a problem, but we should revert to
>> 26 since that is the stable brach of wxWidgets.
sure; that's my fault.
I'm going to set it in wxLua bakefiles so that won't be a problem anymore.


>>  
>>
> I am suprized why it  is not recognized automatically using WXWIN?
WXWIN only gives info about location of wxWidgets, not its version.


>>> How does one deal with stedit in the second target? Maybe that should go
>>> into install.html too.
>>>   
>>
>>
>> What second target?
>>  
>>
> wxluaedit uses stedit, so the second target in that apps.dsw
if I understand it correctly (please remember that it's quite a bit of 
time I'm not using MSVC anymore and I don't have a fresh idea of how 
wxLua project files look and how many are the targets and how they are 
exactly named :)), this is the same problem I have on linux :)

See problem #1 in my "Remaining problems" mails


>>>> Trying to test it.
>>>>
>>>> In the project file wxLua.dsw, VC6 could not find target app_wxLua, it
>>>> seems to search for
>>>> wxLua/apps/build/msw/apps.dsp.
>>>> And indeed i could not find it, although there is apps.dsw.
>>>>
>>>> Can you fix that?
>>>>     
>>
>>
>> apps.dsp has been removed, do another checkout.
anyway I updated apps.dsw to match the new DSP names


> And it is all LF again, so no project file works anymore.
if you are checking out from a win32 box and DSP files were added to CVS 
repository as text files, this should never happen (CVS should check 
them out using CRLF). Maybe they were added as binary.
In frm-bakefile 0.2.0 I have added a --crlf=(native|dos|mac|unix) option 
which I could use to tell bakefile_gen to generate DSW/DSP files always 
with dos EOL...

I'm going to do that ASAP.


>>>> Is there already a cleanall /deep ?  I see that things get mixed up in
>>>> project files, so a real good/all clean like in wxArt2D  is needed i
>>>> think.
I'll test wxLua project files as soon as linux problems are solved...

Francesco

[Wxlua-users] Remaining problems on Linux (Re: wxLua on Linux)

[Francesco M. <f18...@ya...>]

Hi,

John Labenski ha scritto:
> On 1/23/06, Francesco Montorsi <f18...@ya...> wrote:
> 
>>>>>./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is
>>>>>not defined
> Ok, I've added a new setting in wx.rules where you can add any
> additional code for the binding header. There is where I've placed
> 
> #ifndef wxUSE_WAVE
> #define wxUSE_WAVE 0
> #endif
> 
> so that ti should work anywhere. It's a little bit of a hack, but I
> think this is all we can do to maintain backwards compatibility.
I confirm that wxUSE_WAVE warning is disappeared.

Still we have at least the following problems:

1) STC (more generically CONTRIB) problem

2) wxLUA_USE_wxCriticalSectionLocker is not defined - maybe it should be 
added to wxluasetup.h

3) wxLua application needs wxStyledTextCtrl wrapper and an error should 
be given when it's not available instead of just failing it at runtime (IMO)

4) currently doing a thing like:
      mkdir mybuild && cd mybuild && ../configure && make
    doesn't work. I'm going to fix this tomorrow.

5) change the target names to avoid clashes with system installations of 
LUA.


For more info about #1 and #3 please look at my other mails in this same 
thread. For #5 see 'target names' thread.

Francesco

[Wxlua-users] Re: target names

[Francesco M. <f18...@ya...>]

Hi,

k. holwerda ha scritto:
>> I like the two target names to be changed, since else i can not use 
>> them the same way with Cmake.
>> Actually it is more a VC project problem, cmake does generate them 
>> correctly.
>> The problem is that there is a lua executable and a lua library, and 
>> the same for wxlua.
>> Especially the lua itself is causing me problems, since that target is 
>> used to generate the binding too.
>> So it name should be lua(.exe)
>>
>> Can the library names  be changed to wxlual and lual ?
>>
>> ( i wonder anyway what happens if our internal lua is installed, and 
>> it conflicts with a lua lib installed form some other source. So it 
>> might not be a bad idea to name ours different. )
I agree we need to redefine the names of the libraries created by wxLua. 
  Specially to avoid conflicts with LUA libraries installed from other 
sources, if this is necessary.

So,
1) is the lua library compiled with wxLua different from the 
'standard/official' lua library ?
I think it is because I saw the symbol WXLUA_CODE defined when compiling 
lua...

2) how do we name the wxLua libraries ?
    Currently I see in wxLua/lib:

-rw-r--r--  1 frm frm   674700 2006-01-24 10:13 liblua.a
-rw-r--r--  1 frm frm   128872 2006-01-20 13:40 liblualib.a
-rw-r--r--  1 frm frm 13821610 2006-01-25 18:47 libwxbind.a
-rw-r--r--  1 frm frm  1706004 2006-01-24 10:14 libwxlua.a
-rw-r--r--  1 frm frm  1320170 2006-01-24 10:19 libwxluadebug.a
-rw-r--r--  1 frm frm  1812618 2006-01-24 10:19 libwxluasocket.a

but I know that John's hand written makefiles have a more wx-like 
library namings. We could name them as:

      libwxlua_[gtk2|x11|msw|...][u][d]_lua-[wxversion].so.0
      libwxlua_[gtk2|x11|msw|...][u][d]_lualib-[wxversion].so.0
      libwxlua_[gtk2|x11|msw|...][u][d]_wxbind-[wxversion].so.0
      libwxlua_[gtk2|x11|msw|...][u][d]_wxlua-[wxversion].so.0
      libwxlua_[gtk2|x11|msw|...][u][d]_wxluadebug-[wxversion].so.0
      libwxlua_[gtk2|x11|msw|...][u][d]_wxluasocket-[wxversion].so.0

Do you agree ?

Francesco

Re: [Wxlua-users] wxLua on win32

[k. h. <kla...@nl...>]

Hi,

John Labenski wrote:

>>So leafs the not found target.
>>
>>I see in the modules a split in sourse and headers, nice!
>>Can it be made non capital in all cases?
>>
>>In apps.dsw, i get can not open wxmsw27d_xrc.lib, indeed that i don't
>>have ;-)
>>I have wxmsw26d_xrc.lib, how come?
>>    
>>
>
>The last update using bakefile has changed from 26 to 27. I use
>wxWidgets CVS head so this is not a problem, but we should revert to
>26 since that is the stable brach of wxWidgets.
>  
>
I am suprized why it  is not recognized automatically using WXWIN?
All other are oke.

Anyway i changed it to 26 and after correcting all other problems, i did 
get an error in lua.
(wxStyledTextCtrl (a nil value ).

>  
>
>>How does one deal with stedit in the second target? Maybe that should go
>>into install.html too.
>>    
>>
>
>What second target?
>  
>
wxluaedit uses stedit, so the second target in that apps.dsw

>  
>
>>>Trying to test it.
>>>
>>>In the project file wxLua.dsw, VC6 could not find target app_wxLua, it
>>>seems to search for
>>>wxLua/apps/build/msw/apps.dsp.
>>>And indeed i could not find it, although there is apps.dsw.
>>>
>>>Can you fix that?
>>>      
>>>
>
>apps.dsp has been removed, do another checkout.
>  
>
I know that, but it is still referred to from wxLua.dsw.

I just did another checkout,

wxLua.dsw contains this line ( see apps.dsp ), which can not be found.

Project: "app_wxlua"=..\..\apps\build\msw\apps.dsp - Package Owner=<4>

And it is all LF again, so no project file works anymore.

Converting by hand back to CRLF makes apps.dsp the problem again.

Project: "apps_app_wxlua"=..\..\apps\build\msw\apps_app_wxlua.dsp - 
Package Owner=<4>
Project: 
"apps_app_wxluaedit"=..\..\apps\build\msw\apps_app_wxluaedit1.dsp - 
Package Owner=<4>

>  
>
>>>Is there already a cleanall /deep ?  I see that things get mixed up in
>>>project files, so a real good/all clean like in wxArt2D  is needed i
>>>think.
>>>      
>>>
>
>A clean checkout is probably best.
>  
>
No bettter copy that bakefile part from wxArt2D, it should be the same.
Then using the makefiles one can do a proper clean.

Klaas


Unclassified

Re: [Wxlua-users] wxLua on win32

[John L. <jla...@gm...>]

On 1/24/06, klaas.holwerda <kho...@xs...> wrote:
> and in the others i see wxluasetup.h ?
>
> Generated the bindings once more, and no it is luasetup.h all over??
> I wonder what i did  do wrong?

It's called wxluasetup.h now.

> So leafs the not found target.
>
> I see in the modules a split in sourse and headers, nice!
> Can it be made non capital in all cases?
>
> In apps.dsw, i get can not open wxmsw27d_xrc.lib, indeed that i don't
> have ;-)
> I have wxmsw26d_xrc.lib, how come?

The last update using bakefile has changed from 26 to 27. I use
wxWidgets CVS head so this is not a problem, but we should revert to
26 since that is the stable brach of wxWidgets.

> How does one deal with stedit in the second target? Maybe that should go
> into install.html too.

What second target?

> > Trying to test it.
> >
> > In the project file wxLua.dsw, VC6 could not find target app_wxLua, it
> > seems to search for
> > wxLua/apps/build/msw/apps.dsp.
> > And indeed i could not find it, although there is apps.dsw.
> >
> > Can you fix that?

apps.dsp has been removed, do another checkout.

> > Is there already a cleanall /deep ?  I see that things get mixed up in
> > project files, so a real good/all clean like in wxArt2D  is needed i
> > think.

A clean checkout is probably best.

-John

Re: [Wxlua-users] wxLua on win32

[klaas.holwerda <kho...@xs...>]

and in the others i see wxluasetup.h ?

Generated the bindings once more, and no it is luasetup.h all over??
I wonder what i did  do wrong?

So leafs the not found target.

I see in the modules a split in sourse and headers, nice!
Can it be made non capital in all cases?

In apps.dsw, i get can not open wxmsw27d_xrc.lib, indeed that i don't 
have ;-)
I have wxmsw26d_xrc.lib, how come?

How does one deal with stedit in the second target? Maybe that should go 
into install.html too.

Tomorrow i will test more.

regards,

Klaas

klaas.holwerda wrote:

> Hi,
>
> Trying to test it.
>
> In the project file wxLua.dsw, VC6 could not find target app_wxLua, it 
> seems to search for
> wxLua/apps/build/msw/apps.dsp.
> And indeed i could not find it, although there is apps.dsw.
>
> Can you fix that?
>
> Is there already a cleanall /deep ?  I see that things get mixed up in 
> project files, so a real good/all clean like in wxArt2D  is needed i 
> think.
>
> I think we need a install.html.
> At least for now batch build does not work yet, for all configurations 
> (DLL).
> So i just do debug and release from selection in batch build.
>
> mod_wxbind tells me that luasetup.h can not be found? Others or oke.
>
> It is at e.g. print.cpp at #include "luasetup.h"
>
> regards,
>
> Klaas
>
> Francesco Montorsi wrote:
>
>> Hi,
>>     I've tried last wxLua (with my bakefile changes) on win32 with 
>> MSVC .NET; almost everything went fine after setting the WXWIN env 
>> variable, compiling wxWidgets and converting msvc6 projects to a .SLN 
>> file.
>>
>> I say "almost" because I get errors about a wxWinHelpController not 
>> defined and a "new wxDC()" which cannot be done because wxDC is 
>> abstract.
>>
>> This could be because I'm using wxCVS (both on win32 and on linux).
>>
>> Does anyone got my same problems ?
>>
>> Francesco
>>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

Re: [Wxlua-users] wxLua on win32

[klaas.holwerda <kho...@xs...>]

Hi,

Trying to test it.

In the project file wxLua.dsw, VC6 could not find target app_wxLua, it 
seems to search for
wxLua/apps/build/msw/apps.dsp.
And indeed i could not find it, although there is apps.dsw.

Can you fix that?

Is there already a cleanall /deep ?  I see that things get mixed up in 
project files, so a real good/all clean like in wxArt2D  is needed i think.

I think we need a install.html.
At least for now batch build does not work yet, for all configurations 
(DLL).
So i just do debug and release from selection in batch build.
 
mod_wxbind tells me that luasetup.h can not be found? Others or oke.

It is at e.g. print.cpp at #include "luasetup.h"

regards,

Klaas

Francesco Montorsi wrote:

> Hi,
>     I've tried last wxLua (with my bakefile changes) on win32 with 
> MSVC .NET; almost everything went fine after setting the WXWIN env 
> variable, compiling wxWidgets and converting msvc6 projects to a .SLN 
> file.
>
> I say "almost" because I get errors about a wxWinHelpController not 
> defined and a "new wxDC()" which cannot be done because wxDC is abstract.
>
> This could be because I'm using wxCVS (both on win32 and on linux).
>
> Does anyone got my same problems ?
>
> Francesco
>

Re: [Wxlua-users] target names

[k. h. <kla...@nl...>]

Forget this one, i solved using Cmake tricks.

But the install point is still something to think about.

k. holwerda wrote:

> Hi Francesco,
>
> I like the two target names to be changed, since else i can not use 
> them the same way with Cmake.
> Actually it is more a VC project problem, cmake does generate them 
> correctly.
> The problem is that there is a lua executable and a lua library, and 
> the same for wxlua.
> Especially the lua itself is causing me problems, since that target is 
> used to generate the binding too.
> So it name should be lua(.exe)
>
> Can the library names  be changed to wxlual and lual ?
>
> ( i wonder anyway what happens if our internal lua is installed, and 
> it conflicts with a lua lib installed form some other source. So it 
> might not be a bad idea to name ours different. )
>
> thanks,
>
> Klaas
>
>

-- 
Unclassified

[Wxlua-users] target names

[k. h. <kla...@nl...>]

Hi Francesco,

I like the two target names to be changed, since else i can not use them 
the same way with Cmake.
Actually it is more a VC project problem, cmake does generate them 
correctly.
The problem is that there is a lua executable and a lua library, and the 
same for wxlua.
Especially the lua itself is causing me problems, since that target is 
used to generate the binding too.
So it name should be lua(.exe)

Can the library names  be changed to wxlual and lual ?

( i wonder anyway what happens if our internal lua is installed, and it 
conflicts with a lua lib installed form some other source. So it might 
not be a bad idea to name ours different. )

thanks,

Klaas


-- 
Unclassified

Re: [Wxlua-users] Re: wxLua on Linux

[John L. <jla...@gm...>]

On 1/23/06, Francesco Montorsi <f18...@ya...> wrote:
> >>> ./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is
> >>> not defined
> >>> ./../modules/wxbind/include/wxbind.h:328:5: warning:
> >>> "wxLUA_USE_wxCriticalSection" is not defined
> >>
> > Me too, at least the first, i just disabled  it in luasetup.h to make i=
t
> > go away.
> >
> > #define wxLUA_USE_wxWave                        0
> I've found the reason in wx/wave.h:
>
> #if wxUSE_SOUND                         // not wxUSE_WAVE !sdf
> ...
>      #include "wx/sound.h"
>      // wxSound used to be called wxWave before wxWidgets 2.5.1:
>      typedef wxSound wxWave;
> ...
> #endif

Ok, I've added a new setting in wx.rules where you can add any
additional code for the binding header. There is where I've placed

#ifndef wxUSE_WAVE
#define wxUSE_WAVE 0
#endif

so that ti should work anywhere. It's a little bit of a hack, but I
think this is all we can do to maintain backwards compatibility.

Regards,
    John Labenski

[Wxlua-users] wxLua on win32

[Francesco M. <f18...@ya...>]

Hi,
     I've tried last wxLua (with my bakefile changes) on win32 with MSVC 
.NET; almost everything went fine after setting the WXWIN env variable, 
compiling wxWidgets and converting msvc6 projects to a .SLN file.

I say "almost" because I get errors about a wxWinHelpController not 
defined and a "new wxDC()" which cannot be done because wxDC is abstract.

This could be because I'm using wxCVS (both on win32 and on linux).

Does anyone got my same problems ?

Francesco

[Wxlua-users] Re: wxLua on Linux

[Francesco M. <f18...@ya...>]

Hi,

>> /wxlua/src/wxlstate.cpp:1740: undefined reference to 
>> `s_wxluatag_wxWindow'
>> ./wxlua/src/internal.cpp:1049: undefined reference to 
>> `s_wxluatag_wxEvtHandler'
>> ./wxlua/src/internal.cpp:1176: undefined reference to 
>> `s_wxluatag_wxBitmap'
>>
>> I'm still looking to these because now I can see that these symbols 
>> are defined and compiled.
>> Probably I need to play with library order.
>> As soon as I solve this, I'll commit my bakefile changes.
> 
> I've solved linking problems and committed my bakefile changes.
now also make install and uninstall work good.

I've updated the bakefile archive at:
http://www.geocities.com/f18m_cpp217828/frm-bakefile.tar.gz
with a little fix.

Francesco

[Wxlua-users] Re: wxLua on Linux

[Francesco M. <f18...@ya...>]

Hi,

> However I still get undefined reference to:
> 
> /wxlua/src/wxlstate.cpp:1740: undefined reference to `s_wxluatag_wxWindow'
> ./wxlua/src/internal.cpp:1049: undefined reference to 
> `s_wxluatag_wxEvtHandler'
> ./wxlua/src/internal.cpp:1176: undefined reference to `s_wxluatag_wxBitmap'
> 
> I'm still looking to these because now I can see that these symbols are 
> defined and compiled.
> Probably I need to play with library order.
> As soon as I solve this, I'll commit my bakefile changes.
I've solved linking problems and committed my bakefile changes.

Unfortunately I have a problem when running "wxlua" application:

[string "bin/wxlua"]:374: attempt to call field `wxStyledTextCtrl' (a 
nil value)wxLua: Error while running chunkwxLua: Error while running chunk

This is probably because I put wxLUA_USE_StyledTextCtrl to 0; maybe a 
check like:

#if !wxLUA_USE_wxStyledTextCtrl
#error wxLua application needs wxStyledTextCtrl !
#endif

should be added to some wxlua app source code ?

Francesco

[Wxlua-users] Re: wxLua on Linux

[Francesco M. <f18...@ya...>]

Hi,


John Labenski ha scritto:
>>>>Could we commit the generated bindings in CVS ?
>>>
>>>Ok, I'll do that this weekend.
>>
>>good
> 
> 
> Sorry, not yet, let me sort out the coroutine problems first. I have
> some thinking to do about it, it needs to be an elegant solution.
ok


>>>>We also really need some way to:
>>>>1) produce luasetup.h from luasetup.h.in (maybe adding 'wx' prefix to
>>>>both as we discussed time ago): I had to manually change it to exclude
>>>>the contrib wx headers which I do not have installed and wxFontMapper
>>>>(see point #3)
>>>
>>>This is supposed to be like wxWidgets/include/wx/msw/setup0.h where
>>>you select what you want included with your wxLua bindings build. I
>>>will change it to wxluasetup.h this weekend.
>>
>>ok, on win32 I'd keep it exactly like wx's setup0.h but on unix we need
>>(like wx does) a wxluasetup.h.in which is transformed into wxluasetup.h.
> 
> 
> I don't think you need to do anything, there's nothing in it that
> depends on anything that configure could figure out. Hopefully all of
> the bindings take into account the wxWidgets wxUSE_XXX defines
> appropriately and so the wxLUA_USE_XXX are a way to not compile in
> wxLua bindings to parts of the wxWidgets library that either may or
> may not be compiled in. If this is not the case please tell me where
> it's wrong.
now I understood: wxLua bindings are double-"protected" by both 
wxUSE_XXX symbols and wxLUA_USE_XXX ones.

That's good. However I must say that wxbind.h uses very few wxUSE_XXX 
symbols (I understand it's a real trouble to write all those #if/#endif 
by hand - BTW is wxbind.h auto generated ?).

For example, I haven't got the STC headers installed and my compilation 
stops with the error:

./../modules/wxbind/include/wxbind.h:579:24: error: wx/stc/stc.h: No 
such file or directory

Unfortunately there is no wxUSE_STC symbols... this is because STC is a 
contrib.

I think we should separe wxlua contrib wrappers from wxlua wxwidgets 
wrappers and then create a BUILD_CONTRIB_WRAPPERS=0/1 (or something like 
that :)) option to bakefiles.




> 
> 
>>>>2) fix warnings about non-existing symbols (I get ton of messages like:
>>>>
>>>>./modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is not
>>>>defined
>>>>./../modules/wxbind/include/wxbind.h:328:5: warning:
>>>>"wxLUA_USE_wxCriticalSection" is not defined
>>>>./../modules/wxbind/include/wxbind.h:506:5: warning:
>>>>"wxLUA_USE_wxCriticalSectionLocker" is not defined
>>>>./../modules/wxbind/include/wxbind.h:919:5: warning:
>>>>"wxLUA_USE_wxCriticalSectionLocker" is not defined
>>>>./../modules/wxbind/include/wxbind.h:1038:6: warning: "wxUSE_WAVE" is
>>>>not defined
>>>>...
>>>
>>>These should all be defined! I'll get a new cvs head checkout at home
>>>in linux (mine is probably a month old)  and see if I get them. The
>>>wxLUA_USE_XXX are certainly defined in luasetup.h though.
>>
>>I don't know why but the wxUSE_WAVE and
>>wxLUA_USE_wxCriticalSectionLocker symbols are not defined...
> 
> 
> These are all defined in my last wxWidgets checkout, I'm sorry but I
> can't understand why iut doesn't work for you. Could you try some
> things out like putting #if wxUSE_WAVE in the wxWidgets minimal sample
> and see if you get the warning there?
I've found that wxUSE_WAVE is deprecated since wx2.5.1 in favour of 
wxUSE_SOUND.
I also searched all my local wxLua directory for 
wxLUA_USE_wxCriticalSectionLocker and I couldn't found any definition of 
it (I think it should be in wxluasetup.h but it's not). I could just 
found places where it was used (#if wxLUA_USE_wxCriticalSectionLocker...)

should we add it to wxluasetup.h ?

Also, I think we need to write in some doc a list of files which are 
automatically generated. I really have a vague idea about what's auto 
generated and what not :(


In conclusion, since last update, I could build completely wxLua 
*libraries* just changing

#define wxLUA_USE_wxStyledTextCtrl              1

to

#define wxLUA_USE_wxStyledTextCtrl              0

However I still get undefined reference to:

/wxlua/src/wxlstate.cpp:1740: undefined reference to `s_wxluatag_wxWindow'
./wxlua/src/internal.cpp:1049: undefined reference to 
`s_wxluatag_wxEvtHandler'
./wxlua/src/internal.cpp:1176: undefined reference to `s_wxluatag_wxBitmap'

I'm still looking to these because now I can see that these symbols are 
defined and compiled.
Probably I need to play with library order.
As soon as I solve this, I'll commit my bakefile changes.


Francesco

[Wxlua-users] Re: wxLua on Linux

[Francesco M. <f18...@ya...>]

k. holwerda ha scritto:
> 
> 
> John Labenski wrote:
> 
>>> ./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is 
>>> not defined
>>> ./../modules/wxbind/include/wxbind.h:328:5: warning: 
>>> "wxLUA_USE_wxCriticalSection" is not defined
>>>   
>>
>>
>> You seem to only get these two warnings, why only these?
>>  
>>
> Me too, at least the first, i just disabled  it in luasetup.h to make it 
> go away.
> 
> #define wxLUA_USE_wxWave                        0
I've found the reason in wx/wave.h:

#if wxUSE_SOUND				// not wxUSE_WAVE !
...
     #include "wx/sound.h"
     // wxSound used to be called wxWave before wxWidgets 2.5.1:
     typedef wxSound wxWave;
...
#endif

Francesco

Re: [Wxlua-users] Re: wxLua on Linux

[k. h. <kla...@nl...>]

John Labenski wrote:

>>./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is not defined
>>./../modules/wxbind/include/wxbind.h:328:5: warning: "wxLUA_USE_wxCriticalSection" is not defined
>>    
>>
>
>You seem to only get these two warnings, why only these?
>  
>
Me too, at least the first, i just disabled  it in luasetup.h to make it 
go away.

#define wxLUA_USE_wxWave                        0


Klaas

-- 
Unclassified

Re: [Wxlua-users] Re: wxLua on Linux

[John L. <jla...@gm...>]

> >>Could we commit the generated bindings in CVS ?
> >
> > Ok, I'll do that this weekend.
> good

Sorry, not yet, let me sort out the coroutine problems first. I have
some thinking to do about it, it needs to be an elegant solution.

> >>We also really need some way to:
> >>1) produce luasetup.h from luasetup.h.in (maybe adding 'wx' prefix to
> >>both as we discussed time ago): I had to manually change it to exclude
> >>the contrib wx headers which I do not have installed and wxFontMapper
> >>(see point #3)
> >
> > This is supposed to be like wxWidgets/include/wx/msw/setup0.h where
> > you select what you want included with your wxLua bindings build. I
> > will change it to wxluasetup.h this weekend.
> ok, on win32 I'd keep it exactly like wx's setup0.h but on unix we need
> (like wx does) a wxluasetup.h.in which is transformed into wxluasetup.h.

I don't think you need to do anything, there's nothing in it that
depends on anything that configure could figure out. Hopefully all of
the bindings take into account the wxWidgets wxUSE_XXX defines
appropriately and so the wxLUA_USE_XXX are a way to not compile in
wxLua bindings to parts of the wxWidgets library that either may or
may not be compiled in. If this is not the case please tell me where
it's wrong.

> >>2) fix warnings about non-existing symbols (I get ton of messages like:
> >>
> >>./modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is not
> >>defined
> >>./../modules/wxbind/include/wxbind.h:328:5: warning:
> >>"wxLUA_USE_wxCriticalSection" is not defined
> >>./../modules/wxbind/include/wxbind.h:506:5: warning:
> >>"wxLUA_USE_wxCriticalSectionLocker" is not defined
> >>./../modules/wxbind/include/wxbind.h:919:5: warning:
> >>"wxLUA_USE_wxCriticalSectionLocker" is not defined
> >>./../modules/wxbind/include/wxbind.h:1038:6: warning: "wxUSE_WAVE" is
> >>not defined
> >>...
> >
> > These should all be defined! I'll get a new cvs head checkout at home
> > in linux (mine is probably a month old)  and see if I get them. The
> > wxLUA_USE_XXX are certainly defined in luasetup.h though.
> I don't know why but the wxUSE_WAVE and
> wxLUA_USE_wxCriticalSectionLocker symbols are not defined...

These are all defined in my last wxWidgets checkout, I'm sorry but I
can't understand why iut doesn't work for you. Could you try some
things out like putting #if wxUSE_WAVE in the wxWidgets minimal sample
and see if you get the warning there?

> >>3) now compilation stops on my file:
> >>
> >>./wxbind/src/gdi.cpp:2289: error: 'class wxFontMapper' has no member
> >>named 'SetConfig'

Fixed.

> .././bk-deps g++ -c -o wxbind_lib_wx_class.o -I./../modules -I/usr/local/=
lib/wx/include/gtk2-ansi-debug-static-2.7 -I/usr/local/include/wx-2.7 -D_FI=
LE_OFFSET_BITS=3D64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=3D1 -D__WXDEBUG__ -D=
__WXGTK__ -pthread  -g -O0 -Wall -Wundef -Wno-ctor-dtor-privacy ./wxbind/sr=
c/wx_class.cpp
> In file included from ./wxbind/src/wx_class.cpp:26:
> ./../modules/wxbind/include/wxbind.h:127:6: warning: "wxUSE_WAVE" is not =
defined
> ./../modules/wxbind/include/wxbind.h:328:5: warning: "wxLUA_USE_wxCritica=
lSection" is not defined

You seem to only get these two warnings, why only these?

> ./wxbind/src/wx_class.cpp: In function 'void wxLua_addToTrackedMemoryList=
(wxLuaState&, wxTreeItemId*)':

All of these are fixed, hopefully.

Regards,
    John Labenski