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