wxlua-users

[Wxlua-users] Bakefile

[f18m_217828 <f18...@ya...>]

Hi,
    in the next week, I'd like to contribute bakefiles for the wxLua 
project. If this okay, then this sunday (the next 2 days I won't be able 
to read emails) I'll start to work on it.

My SF id is "frm" so if you grant me write permissions I'll commit to 
the CVS the bakefiles.

Unfortunately, I've never used wxLua before (even if I already have 
bakefiles ready for lua) so I need to fully understand what such build 
system should do.

Please, can you give me a short summary about this ?
Which libraries should be created from which source files and where 
should the output go ?
Which executables should be created ?
Does wxLua supports unicode & shared builds ?
Are there additional tasks which the build system should take on ?

Thanks,
Francesco Montorsi

Re: [Wxlua-users] Bakefile

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

On 6/2/05, f18m_217828 <f18...@ya...> wrote:
>     in the next week, I'd like to contribute bakefiles for the wxLua
> project. If this okay, then this sunday (the next 2 days I won't be able
> to read emails) I'll start to work on it.

This would be great, but! We gotta get the dir structure down first.
Wait for a message saying that it's done.

See the end of this message for my proposal:
"Directory structure (was Re: wxlua.sourceforge.net is opened)"
=20
I want to hear some Yea/Nays about it before I go through the trouble
of moving things. If you'd rather have it differently please post your
own full dir structure, I'm open to anything so long as we agree. I'm
finding the little snippits hard to understand and want to see the
whole thing to understand it. I don't want to do anything until I hear
people say, "yes, I can live with that, go ahead and move things"
since it really is a pain.

> My SF id is "frm" so if you grant me write permissions I'll commit to
> the CVS the bakefiles.

You are part of wxArt2D? It would be ok to add you by me.

> Unfortunately, I've never used wxLua before (even if I already have
> bakefiles ready for lua) so I need to fully understand what such build
> system should do.
>=20
> Please, can you give me a short summary about this ?
> Which libraries should be created from which source files and where
> should the output go ?
> Which executables should be created ?
> Does wxLua supports unicode & shared builds ?
> Are there additional tasks which the build system should take on ?

See newdirs.txt here.=20
http://cvs.sourceforge.net/viewcvs.py/wxlua/wxLua/docs/

I will update it once we figure out the dirs and describe what goes
where and how, so don't write anything based on it right now.

Regards,
    John Labenski

Re: [Wxlua-users] Bakefile

[f18m_217828 <f18...@ya...>]

Hi,

 > This would be great, but! We gotta get the dir structure down first.
 > Wait for a message saying that it's done.
ok; I'm waiting ;-)

 > I want to hear some Yea/Nays about it before I go through the trouble
 > of moving things. If you'd rather have it differently please post your
 > own full dir structure, I'm open to anything so long as we agree. I'm
 > finding the little snippits hard to understand and want to see the
 > whole thing to understand it. I don't want to do anything until I hear
 > people say, "yes, I can live with that, go ahead and move things"
 > since it really is a pain.
ok, as I said earlier I advise to use lowercase filenames & dirnames.
I'm now going to read the mails about dir structure; I'll let you know 
something if I think the dir structure can be improved...

 >> My SF id is "frm" so if you grant me write permissions I'll commit to
 >> the CVS the bakefiles.
 >
 > You are part of wxArt2D? It would be ok to add you by me.
I'm currently contributing bakefiles to wxArt2d (and so I'm listed as 
wxart2d developer) since I'm going to use it in my projects :-)
Since wxLua is a wxArt2d dependency I'd like to have wxLua bakefilized, too.

 >> Which libraries should be created from which source files and where
 >> should the output go ?
 >> Which executables should be created ?
 >> Does wxLua supports unicode & shared builds ?
 >> Are there additional tasks which the build system should take on ?
 >
 > See newdirs.txt here. 
http://cvs.sourceforge.net/viewcvs.py/wxlua/wxLua/docs/
 >
 > I will update it once we figure out the dirs and describe what goes
 > where and how, so don't write anything based on it right now.
okay, just let me know when you have definitively set up everything.

Francesco Montorsi

PS: I would correct GNUMailman standard behaviour so that the "reply-to" 
field of all mails are set to wxl...@li... and not 
to the sender of the mail ;-)

Re: [Wxlua-users] Bakefile

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

Hi,

 > Thanks, see the last message of mine called "Dir structure".

I'm looking at my just-checked out wxLua module and I have some questions...

1) I see wxLua\src & wxLua\include are not listed in dirs.txt; should 
they be removed ?

2) The targets which need to be built are:
- modules\lua
- modules\wxlua
- modules\wxluadebug
- modules\wxluasocket
and they must be built as libraries, right ?
Do they support shared (i.e. DLL) builds ?
Do they support Unicode builds ?
Except for lua, all others are wx-based, right ?
All the output should go to wxArt2d\lib, right ?

3) the target wxLua\apps\wxlua does depend from all the modules listed 
in wxLua\modules ?
Does it supports shared & unicode builds ?
Its output should go to wxArt2d\bin, right ?

4) in wxLua\bindings\wxwidgets there are some CPP & H files; should they 
be built as a library ?
If yes, how should that lib be called ?

Assuming all replies are yes, I'd organize bakefile build system as follow:

wxLua
|-build
| |- msw
| |- bakefiles
|
|-modules
| |-build
|   |- msw
|   |- bakefiles
|
|-apps
| |-build
| | |- msw
| | |- bakefiles
| |-wxlua
|   |-build
|     |- msw
|     |- bakefiles
|
|-utils
| |-build
|   |- msw
|   |- bakefiles

to build the project, the user should just go to wxlua\build\msw and type

nmake -fmakefile.vc WX_UNICODE=0/1 WX_SHARED=0/1 ....

Do you like this approach ?

Let me know,
Francesco Montorsi

PS: I see that exists a file called luasetup.h in 
wxlua\bindings\wxwidgets; what is its use ? should it be generated by 
some tool/makefile ?

PS2: does wxLua builds in linux ?

PS3: please fix the reply-to behaviour of this list: I really do not 
understand why mailman software sets to default the reply-to field to 
the sender of the mail instead of the mailing list itself !

Re: [Wxlua-users] Bakefile

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

On 6/11/05, Francesco Montorsi <f18...@ya...> wrote:
> > Thanks, see the last message of mine called "Dir structure".
> I'm looking at my just-checked out wxLua module and I have some questions=
...
>=20
> 1) I see wxLua\src & wxLua\include are not listed in dirs.txt; should
> they be removed ?

Yes, but let's leave them for now since they still have one file in
them that Ray says he doesn't want, but it probably wouldn't hurt to
let it be for a bit.
=20
> 2) The targets which need to be built are:
> - modules\lua
> - modules\wxlua
> - modules\wxluadebug
> - modules\wxluasocket
for modules/lua you need to build two things, lua.exe the lua
executable and lua.lib the library. lua should be built as a static
lib on all platforms, see the Makefiles and dsp files to see how it's
done.
Maybe you can take a look at these bakefiles to see if they'll work for us
http://lua-users.org/wiki/LuaAddons
http://www.geocities.com/f18m_cpp217828/prog/lua_win32.zip

> and they must be built as libraries, right ?
Yes.

> Do they support shared (i.e. DLL) builds ?
Hopefully yes, I've never build wxWidgets as a DLL, but I copied the
code in the wxWidget's contrib and added WXDLLIMPEXP_WXLUA which
should export things properly. I have no idea about lua itself though.

> Do they support Unicode builds ?
Yes, all except lua.

> Except for lua, all others are wx-based, right ?
Yes, all Makefiles and wxXXX_wx26.dsp/w in the src/ dirs work properly
so you can get the proper include dirs and flags from them.

> All the output should go to wxArt2d\lib, right ?
No? It goes to wxLua/lib for the libraries and lua.exe goes to
wxLua/bin this is a standalone library that anyone can use.

> 3) the target wxLua\apps\wxlua does depend from all the modules listed
> in wxLua\modules ?
Yes.

> Does it supports shared & unicode builds ?
Yes.
> Its output should go to wxArt2d\bin, right ?
No, it should be built in either wxLua/bin or just
wxLua/apps/wxlua/src/vc_xxx for VC for example, in much the same way
wxWidgets builds it's samples.

> 4) in wxLua\bindings\wxwidgets there are some CPP & H files; should they
> be built as a library ?
> If yes, how should that lib be called ?

No, for now they're included directly into the wrappers which is
probably the simplest solution for now. Thew whole wrapper thing is
going to change somehow...

> Assuming all replies are yes, I'd organize bakefile build system as follo=
w:
>=20
> wxLua
> |-build
> | |- msw
> | |- bakefiles
> |
> |-modules
> | |-build
> |   |- msw
> |   |- bakefiles
> |
> |-apps
> | |-build
> | | |- msw
> | | |- bakefiles
> | |-wxlua
> |   |-build
> |     |- msw
> |     |- bakefiles
> |
> |-utils
> | |-build
> |   |- msw
> |   |- bakefiles

Maybe we could put apps/wxlua/build into just apps/build to simplify things=
.

> to build the project, the user should just go to wxlua\build\msw and type
>=20
> nmake -fmakefile.vc WX_UNICODE=3D0/1 WX_SHARED=3D0/1 ....

That would be great, maybe we could also have a dsw file as well, see
apps/wxlua/src/wxLua.dsw that can build all the libraries using "batch
build" just like wx.dsw.

> Do you like this approach ?

It's be great if you can get it working.

> Let me know,
> Francesco Montorsi
>=20
> PS: I see that exists a file called luasetup.h in
> wxlua\bindings\wxwidgets; what is its use ? should it be generated by
> some tool/makefile ?

When you run bindings/wxluawrap.lua it takes either the luasetup.h.in
the bindings dir or in your own program's dir and generates luasetup.h
that may exclude other classes automatically using their dependencies.
It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and
Makefile_import to see how the wrappers are generated. It's build is
also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to
generate wxluawrap.cpp, can bakefile do this sort of thing?

> PS2: does wxLua builds in linux ?

Yup, using the makefiles that use wx-config.

>PS3: please fix the reply-to behaviour of this list: I really do not
>understand why mailman software sets to default the reply-to field to
>the sender of the mail instead of the mailing list itself !

It's fixed now, but the after the message you responded to. Any new
messages from now on should have the correct reply to. Thanks, Klaas.

Re: [Wxlua-users] Bakefile

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

Hi,

>>1) I see wxLua\src & wxLua\include are not listed in dirs.txt; should
>>they be removed ?
> Yes, but let's leave them for now since they still have one file in
> them that Ray says he doesn't want, but it probably wouldn't hurt to
> let it be for a bit.
ok, no problem


>>2) The targets which need to be built are:
>>- modules\lua
>>- modules\wxlua
>>- modules\wxluadebug
>>- modules\wxluasocket
> 
> for modules/lua you need to build two things, lua.exe the lua
> executable and lua.lib the library. lua should be built as a static
> lib on all platforms, see the Makefiles and dsp files to see how it's
> done.
> Maybe you can take a look at these bakefiles to see if they'll work for us
> http://lua-users.org/wiki/LuaAddons
> http://www.geocities.com/f18m_cpp217828/prog/lua_win32.zip
yes, they'll work for us since I created them and uploaded the links 
above in lua wiki & on my website ;-)

>>Do they support shared (i.e. DLL) builds ?
> Hopefully yes, I've never build wxWidgets as a DLL, but I copied the
> code in the wxWidget's contrib and added WXDLLIMPEXP_WXLUA which
> should export things properly. I have no idea about lua itself though.
ok, I'll try


>>All the output should go to wxArt2d\lib, right ?
> No? It goes to wxLua/lib for the libraries and lua.exe goes to
> wxLua/bin this is a standalone library that anyone can use.
oops; I just meant wxLua/lib & wxLua/bin... sorry

>>Its output should go to wxArt2d\bin, right ?
> 
> No, it should be built in either wxLua/bin or just
> wxLua/apps/wxlua/src/vc_xxx for VC for example, in much the same way
> wxWidgets builds it's samples.
again I mistyped the path...


>>4) in wxLua\bindings\wxwidgets there are some CPP & H files; should they
>>be built as a library ?
>>If yes, how should that lib be called ?
> 
> No, for now they're included directly into the wrappers which is
> probably the simplest solution for now. Thew whole wrapper thing is
> going to change somehow...
ok

> Maybe we could put apps/wxlua/build into just apps/build to simplify things.
right, that makes things more simmetric :-)

>>to build the project, the user should just go to wxlua\build\msw and type
>>
>>nmake -fmakefile.vc WX_UNICODE=0/1 WX_SHARED=0/1 ....
> 
> 
> That would be great, maybe we could also have a dsw file as well, see
> apps/wxlua/src/wxLua.dsw that can build all the libraries using "batch
> build" just like wx.dsw.
sure; exactly like wxWidgets also have DSW/DSP files.

>>PS: I see that exists a file called luasetup.h in
>>wxlua\bindings\wxwidgets; what is its use ? should it be generated by
>>some tool/makefile ?
> When you run bindings/wxluawrap.lua it takes either the luasetup.h.in
> the bindings dir or in your own program's dir and generates luasetup.h
> that may exclude other classes automatically using their dependencies.
> It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and
> Makefile_import to see how the wrappers are generated. It's build is
> also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to
> generate wxluawrap.cpp, can bakefile do this sort of thing?
yes, it can; I'll set up all this stuff when done with modules bakefile; 
first I'll create modules\build stuff...

I'll let you know,
Francesco

Re: [Wxlua-users] Bakefile

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

Thanks for all your work.=20

I'm slowly merging wxIDE's cdlua's code and wrappers, but it's slow
going. I hope to have it done be the end of the week and then everyone
can just use this version of wxLua.

Regards,
    John Labenski

On 6/12/05, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>=20
> >>1) I see wxLua\src & wxLua\include are not listed in dirs.txt; should
> >>they be removed ?
> > Yes, but let's leave them for now since they still have one file in
> > them that Ray says he doesn't want, but it probably wouldn't hurt to
> > let it be for a bit.
> ok, no problem
>=20
>=20
> >>2) The targets which need to be built are:
> >>- modules\lua
> >>- modules\wxlua
> >>- modules\wxluadebug
> >>- modules\wxluasocket
> >
> > for modules/lua you need to build two things, lua.exe the lua
> > executable and lua.lib the library. lua should be built as a static
> > lib on all platforms, see the Makefiles and dsp files to see how it's
> > done.
> > Maybe you can take a look at these bakefiles to see if they'll work for=
 us
> > http://lua-users.org/wiki/LuaAddons
> > http://www.geocities.com/f18m_cpp217828/prog/lua_win32.zip
> yes, they'll work for us since I created them and uploaded the links
> above in lua wiki & on my website ;-)
>=20
> >>Do they support shared (i.e. DLL) builds ?
> > Hopefully yes, I've never build wxWidgets as a DLL, but I copied the
> > code in the wxWidget's contrib and added WXDLLIMPEXP_WXLUA which
> > should export things properly. I have no idea about lua itself though.
> ok, I'll try
>=20
>=20
> >>All the output should go to wxArt2d\lib, right ?
> > No? It goes to wxLua/lib for the libraries and lua.exe goes to
> > wxLua/bin this is a standalone library that anyone can use.
> oops; I just meant wxLua/lib & wxLua/bin... sorry
>=20
> >>Its output should go to wxArt2d\bin, right ?
> >
> > No, it should be built in either wxLua/bin or just
> > wxLua/apps/wxlua/src/vc_xxx for VC for example, in much the same way
> > wxWidgets builds it's samples.
> again I mistyped the path...
>=20
>=20
> >>4) in wxLua\bindings\wxwidgets there are some CPP & H files; should the=
y
> >>be built as a library ?
> >>If yes, how should that lib be called ?
> >
> > No, for now they're included directly into the wrappers which is
> > probably the simplest solution for now. Thew whole wrapper thing is
> > going to change somehow...
> ok
>=20
> > Maybe we could put apps/wxlua/build into just apps/build to simplify th=
ings.
> right, that makes things more simmetric :-)
>=20
> >>to build the project, the user should just go to wxlua\build\msw and ty=
pe
> >>
> >>nmake -fmakefile.vc WX_UNICODE=3D0/1 WX_SHARED=3D0/1 ....
> >
> >
> > That would be great, maybe we could also have a dsw file as well, see
> > apps/wxlua/src/wxLua.dsw that can build all the libraries using "batch
> > build" just like wx.dsw.
> sure; exactly like wxWidgets also have DSW/DSP files.
>=20
> >>PS: I see that exists a file called luasetup.h in
> >>wxlua\bindings\wxwidgets; what is its use ? should it be generated by
> >>some tool/makefile ?
> > When you run bindings/wxluawrap.lua it takes either the luasetup.h.in
> > the bindings dir or in your own program's dir and generates luasetup.h
> > that may exclude other classes automatically using their dependencies.
> > It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and
> > Makefile_import to see how the wrappers are generated. It's build is
> > also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to
> > generate wxluawrap.cpp, can bakefile do this sort of thing?
> yes, it can; I'll set up all this stuff when done with modules bakefile;
> first I'll create modules\build stuff...
>=20
> I'll let you know,
> Francesco
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you sho=
tput
> a projector? How fast can you ride your desk chair down the office luge t=
rack?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Re: [Wxlua-users] Bakefile

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

Hi,
   now wxLua bakefiles are in good state: you should be able to use them 
(from command-line) to build all modules & bin2c.
I have some problem with apps\wxlua: when compiling with

nmake -fmakefile.vc WX_UNICODE=1

I get:

Microsoft (R) Program Maintenance Utility   Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.

         ..\..\..\bin\lua -e"target=\"msw\"" ..\..\wxlua\src\wrap.lua

Finding wxWindows Path Using Environment Variable : WXWIN=c:\wxWidgets
Target is : msw
Parsing wxWindows Version File: c:\wxWidgets/include/wx/version.h
Parsing wxWindows Setup File: c:\wxWidgets/include/wx/msw/setup.h
Setup: Compatibility For wxWindows Version 2.4
Output File: wxluawrap.cpp
Parsing Lua Setup File: luasetup.h.in
..\..\..\bin\lua: ../../../bindings/wxluawrap.lua:1834: bad argument #1 
to `line
s' (No such file or directory)
stack traceback:
         [C]: in function `lines'
         ../../../bindings/wxluawrap.lua:1834: in function `ReadSetupFiles'
         ../../../bindings/wxluawrap.lua:1909: in function `main'
         ../../../bindings/wxluawrap.lua:3225: in main chunk
         [C]: in function `dofile'
         ..\..\wxlua\src\wrap.lua:11: in main chunk
         [C]: ?
NMAKE : fatal error U1077: '..\..\..\bin\lua' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Programmi\Microsoft Visual 
Studio\VC98\bin\NMAKE
.EXE"' : return code '0x2'
Stop.

I put that step (..\..\..\bin\lua -e"target=\"msw\"" 
..\..\wxlua\src\wrap.lua) looking at the DSP file... what am I missing ?


>> When you run bindings/wxluawrap.lua it takes either the luasetup.h.in
>> the bindings dir or in your own program's dir and generates luasetup.h
>> that may exclude other classes automatically using their dependencies.
>> It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and
>> Makefile_import to see how the wrappers are generated. It's build is
>> also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to
>> generate wxluawrap.cpp, can bakefile do this sort of thing?
as you can see from the output log above, I created a target in 
makefiles ("wrap") which calls the lua.exe file on 
apps/wxlua/src/wrap.lua... the only problem is that bakefile does not 
know how to build files with extension ".i" so I had to include in 
apps\wxlua sources the file bindings\wxwidgets\wxluawrap.c which the 
makefiles generate just copying the bindings\wxwidgets\wxluawrap.i 
file... this is the only problem I've found.

Let me know,
Francesco

Re: [Wxlua-users] Bakefile

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

On 6/14/05, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>    now wxLua bakefiles are in good state: you should be able to use them
> (from command-line) to build all modules & bin2c.
> I have some problem with apps\wxlua: when compiling with
>=20
> nmake -fmakefile.vc WX_UNICODE=3D1

From what dir?

> I get:
> Microsoft (R) Program Maintenance Utility   Version 6.00.8168.0
> Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
>          ..\..\..\bin\lua -e"target=3D\"msw\"" ..\..\wxlua\src\wrap.lua
> Finding wxWindows Path Using Environment Variable : WXWIN=3Dc:\wxWidgets
> Target is : msw
> Parsing wxWindows Version File: c:\wxWidgets/include/wx/version.h
> Parsing wxWindows Setup File: c:\wxWidgets/include/wx/msw/setup.h
> Setup: Compatibility For wxWindows Version 2.4
> Output File: wxluawrap.cpp
> Parsing Lua Setup File: luasetup.h.in
> ..\..\..\bin\lua: ../../../bindings/wxluawrap.lua:1834: bad argument #1
> to `line
> s' (No such file or directory)
> stack traceback:
>          [C]: in function `lines'
>          ../../../bindings/wxluawrap.lua:1834: in function `ReadSetupFile=
s'
>          ../../../bindings/wxluawrap.lua:1909: in function `main'
>          ../../../bindings/wxluawrap.lua:3225: in main chunk
>          [C]: in function `dofile'
>          ..\..\wxlua\src\wrap.lua:11: in main chunk
>          [C]: ?
> NMAKE : fatal error U1077: '..\..\..\bin\lua' : return code '0x1'
> Stop.
> NMAKE : fatal error U1077: '"C:\Programmi\Microsoft Visual
> Studio\VC98\bin\NMAKE
> .EXE"' : return code '0x2'
> Stop.
>=20
> I put that step (..\..\..\bin\lua -e"target=3D\"msw\""
> ..\..\wxlua\src\wrap.lua) looking at the DSP file... what am I missing ?

You need to make sure that the dirs are correct. We have to use all
relative paths so that if you're building in wxLua/build/msw you
probably have to have something like this.
First go to apps/wxlua/src dir then run wrap.bat (or directly call
wrap.lua as you do) then go back to build/msw.
cd ..\..\apps\wxlua\src && "wrap.bat" && cd ..\..\..\build\msw=20

> >> When you run bindings/wxluawrap.lua it takes either the luasetup.h.in
> >> the bindings dir or in your own program's dir and generates luasetup.h
> >> that may exclude other classes automatically using their dependencies.
> >> It can be updated by hand. Please see apps/wxlua/wrap.bat/lua and
> >> Makefile_import to see how the wrappers are generated. It's build is
> >> also automated in apps/wxlua/src/wxlua_wx26.dsp running wrap.bat to
> >> generate wxluawrap.cpp, can bakefile do this sort of thing?
> as you can see from the output log above, I created a target in
> makefiles ("wrap") which calls the lua.exe file on
> apps/wxlua/src/wrap.lua... the only problem is that bakefile does not
> know how to build files with extension ".i" so I had to include in
> apps\wxlua sources the file bindings\wxwidgets\wxluawrap.c which the
> makefiles generate just copying the bindings\wxwidgets\wxluawrap.i
> file... this is the only problem I've found.

Don't spend too much time on this, we'll be using a whole different
set to wrappers soon.
Something like this, where we can build a lib out of it or just
include them in your project.
 http://cvs.sourceforge.net/viewcvs.py/wxstudio/wxIDE/parts/cdlua/wxbind/

I'm having a hard time understanding the code to do it though.

-John Labenski

Re: [Wxlua-users] Bakefile

[f18m_217828 <f18...@ya...>]

Hi,
    I have updated wxLua bakefiles & makefiles so that it compiles also 
wxbind module.

However, I have two issues to ask:

1) the auto-generated files by "genwxbin.bat" are not in the CVS; this 
is okay to me but I'd need to know if bakefile build system needs to 
call it (this is not a problem) to generate the wxbind source files or 
those files, missing in the CVS, will be included in the releases of 
wxLua (and thus bakefile should not call that batch file)...

2) I now get some error while trying to compile the wxbind module:

         cl /c /nologo /TP /Fomsvcud\wxbind_lib_wx_define.obj /MDd 
/DWIN32 /D_UNI
CODE  /D__WXDEBUG__ /D__WXMSW__  /IT:\wxWidgets\lib\vc_lib\mswud 
/IT:\wxWidgets
\include /I..\..\..\modules /W4 /Od  /Zi 
/Fd..\..\..\lib\vc_lib\wxbind.pdb /D_DE
BUG   /IT:\wxWidgets\contrib\include /GR /EHsc 
..\..\wxbind\src\wx_define.cpp

wx_define.cpp
wx/wave.h header is deprecated, use wx/sound.h and wxSound
..\..\wxbind\src\wx_define.cpp(1511) : error C2065: 
'CB_LEFT_BAR_HANDLE_HITTED'
: undeclared identifier
..\..\wxbind\src\wx_define.cpp(1567) : error C2065: 
'CB_RIGHT_BAR_HANDLE_HITTED'
  : undeclared identifier
..\..\wxbind\src\wx_define.cpp(1596) : error C2065: 
'CB_BAR_CONTENT_HITTED' : un
declared identifier
..\..\wxbind\src\wx_define.cpp(1643) : error C2065: 'wxEOL_MAC' : 
undeclared ide
ntifier
..\..\wxbind\src\wx_define.cpp(1681) : error C2065: 'wxEOL_NATIVE' : 
undeclared
identifier
..\..\wxbind\src\wx_define.cpp(1716) : error C2065: 'CB_NO_ITEMS_HITTED' 
: undec
lared identifier
..\..\wxbind\src\wx_define.cpp(1782) : error C2065: 
'CB_LOWER_ROW_HANDLE_HITTED'
  : undeclared identifier
..\..\wxbind\src\wx_define.cpp(1807) : error C2065: 
'CB_UPPER_ROW_HANDLE_HITTED'
  : undeclared identifier
..\..\wxbind\src\wx_define.cpp(1899) : error C2065: 'wxEOL_UNIX' : 
undeclared id
entifier
..\..\wxbind\src\wx_define.cpp(2101) : error C2065: 'wxEOL_DOS' : 
undeclared ide
ntifier
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Programmi\Microsoft Visual 
Studio\VC98\bin\NMAKE
.EXE"' : return code '0x2'
Stop.


Also, the first message:
"wx/wave.h header is deprecated, use wx/sound.h and wxSound" is repeated 
in each file of wxbind module since it's included in wxbind.h...

3) I see that "luad.exe" has been added in the CVS bin folder:
- is this wanted ?
- bakefile builds lua exe always with the name 'lua.exe'; should I 
change it to build 'luad.exe' when debug is enabled ?
I'd say no because genwxbind.bat does not know which version (build or 
release) of lua has been built and so it needs to refer to the same 
executable name, 'lua.exe', in every build config...

4) I'll start linux build testing asap... I'll let you know

5) I've added DSW/DSP files to CVS so that wxLua can be built also using 
bakefile-generated project files...
however, until bakefile build system does not perfectly work I'd keep 
the current dsw files scattered in modules dirs...

Francesco Montorsi

Re: [Wxlua-users] Bakefile

[f18m_217828 <f18...@ya...>]

6) where should I write bakefile build system docs (both for users' 
usage info and for some internal notes for modifying the build system 
itself...) ?
I'd propose to create an install.html file in root folder where we put 
all this infos...

Francesco

Re: [Wxlua-users] Bakefile

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

On 6/20/05, f18m_217828 <f18...@ya...> wrote:
> Hi,
>     I have updated wxLua bakefiles & makefiles so that it compiles also
> wxbind module.
>=20
> However, I have two issues to ask:
>=20
> 1) the auto-generated files by "genwxbin.bat" are not in the CVS; this
> is okay to me but I'd need to know if bakefile build system needs to
> call it (this is not a problem) to generate the wxbind source files or
> those files, missing in the CVS, will be included in the releases of
> wxLua (and thus bakefile should not call that batch file)...

Lets, not put them up just yet, people will have to run genwxbind.bat
or do the equivalent to generate them. I wouldn't bother generating
them using bakefiles either. We have some cleaning up to do first.
Eventually we'll just have all the cpp files in wxbind/src all the
time since they'll have #ifdefs to work under any condition (but not
yet).
=20
> 2) I now get some error while trying to compile the wxbind module:
>          cl /c /nologo /TP /Fomsvcud\wxbind_lib_wx_define.obj /MDd
...
> ..\..\wxbind\src\wx_define.cpp
>=20
> wx_define.cpp
> wx/wave.h header is deprecated, use wx/sound.h and wxSound

Yes, %if wxLUA_USE_WAVE is being ignored and we haven't added wxSound
instead, ignore this warning for now.

> ..\..\wxbind\src\wx_define.cpp(1511) : error C2065:
> 'CB_LEFT_BAR_HANDLE_HITTED'
> : undeclared identifier

Just set these values to 0, they're from the contrib/include/fl/
library. Again the %if wxLUA_USE_FL is being ignored. You'll have to
do this everytime you run genwxbind.lua until genwxbind.lua gets
fixed.

> ..\..\wxbind\src\wx_define.cpp(1899) : error C2065: 'wxEOL_UNIX' :
> undeclared identifier

put #include "wx/txtstrm.h" at the top of wx_define.cpp, somehow it's
getting skipped even though it's at the bottom of defutils.i. It
probably has something to do with the %enums before it. Again, this is
an issue with genwxbind.lua.

> 3) I see that "luad.exe" has been added in the CVS bin folder:
> - is this wanted ?

No, you should be able to build this on the fly. We should remove it
since every time you build wxlua's lua it'll get overwritten and get
uploaded again (as I did by accident).

> - bakefile builds lua exe always with the name 'lua.exe'; should I
> change it to build 'luad.exe' when debug is enabled ?
> I'd say no because genwxbind.bat does not know which version (build or
> release) of lua has been built and so it needs to refer to the same
> executable name, 'lua.exe', in every build config...

There probably isn't any reason to build lua.exe in debug ever, (that
should always work) but I just wanted to give them different names.
You're probably right though, it'll make things easier to just output
the release and debug versions right on top of each other and leave it
up to the user to remember what they did last. I'll change my dsp
files accordingly.
=20
> 4) I'll start linux build testing asap... I'll let you know

We're a little stuck until we get the %builtin wrappers working since
it's hard to test. Also use samples/editor.wx.lua by running wxLua
../../../samples/editor.wx.lua since the default uses the binary
editor.h which hasn't been updated yet. You get some errors, but the
GUI works.
=20
> 5) I've added DSW/DSP files to CVS so that wxLua can be built also using
> bakefile-generated project files...
> however, until bakefile build system does not perfectly work I'd keep
> the current dsw files scattered in modules dirs...

Yes, I use the XXX_wx26 ones, you're right, I'll remove them once
things get working.

>6) where should I write bakefile build system docs (both for users'
>usage info and for some internal notes for modifying the build system
>itself...) ?
>I'd propose to create an install.html file in root folder where we put
>all this infos...

I think it should go into the docs folder, don't you think? People
should be able to find it easily enough.

-----=20

Sorry, things are a little messed up right now, as Ray said this may
take a little time to get sorted out. Don't bother remming things out
in the .i files (or at least don't commit the changes) since once
genwxbind is working again we'll have to restore them.

-John Labenski