Re: [wxlua-users] build system update (was Re: wxLua now uses an unmodified copy of lua 5.1.1)

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

These warnings are back, I'm pretty sure I didn't get them a week ago
and I don't understand what the problem could be. I'm using wxWidgets
2.6 from CVS and MS Visual Studio 6.

--------------------Configuration: mod_verbatimlua - Win32 Debug
Multilib--------------------
Compiling...
lapi.c
...
lzio.c
Generating Code...
Creating library...
--------------------Configuration: mod_wxlua - Win32 Debug
Multilib--------------------
Compiling...
dummy.cpp
Compiling...
wxlbind.cpp
wxlcallb.cpp
wxlstate.cpp
Generating Code...
Creating library...
--------------------Configuration: mod_wxbind - Win32 Debug
Multilib--------------------
Compiling...
dummy.cpp
Compiling...
appframe.cpp
...
xml.cpp
Generating Code...
Creating library...
wxlua_msw26d_lua.lib(lapi.obj) : warning LNK4006: _lua_ident already
defined in wxlua_msw26d_wxlua.lib(lapi.obj); second definition ignored
wxlua_msw26d_lua.lib(lapi.obj) : warning LNK4006: _luaA_pushobject
already defined in wxlua_msw26d_wxlua.lib(lapi.obj); second definition
ignored
wxlua_msw26d_lua.lib(lzio.obj) : warning LNK4006: _luaZ_openspace
already defined in wxlua_msw26d_wxlua.lib(lzio.obj); second definition
ignored
...
--------------------Configuration: mod_wxbindstc - Win32 Debug
Multilib--------------------
Compiling...
dummy.cpp
Compiling...
stc.cpp
wxstc_bind.cpp
Generating Code...
Creating library...
wxlua_msw26d_lua.lib(lapi.obj) : warning LNK4006: _lua_ident already
defined in wxlua_msw26d_wxlua.lib(lapi.obj); second definition ignored
wxlua_msw26d_lua.lib(lapi.obj) : warning LNK4006: _luaA_pushobject
already defined in wxlua_msw26d_wxlua.lib(lapi.obj); second definition
ignored

and so on for the other libs. Any ideas why this is happening again? I
can't understand why the const char lua_ident[] = {...} inside of
lapi.c only (not in header at all) could possibly have a problem since
mod_wxbind Debug Multilib doesn't link to anything!

On 12/10/06, Francesco Montorsi <f18...@ya...> wrote:
> klaas.holwerda ha scritto:
> > John Labenski wrote:
> >>
> >> What about just using the wxlike-lib for wxlua too? That way the
> >> wxCode bakefiles will be able to use the libs it generates very
> >> easily. This is why I'm so interested in naming all the libs using
> >> wxWidgets like the wxWidgets libs since it becomes easy to mix
> >> everything together.
> >>
> > So i think you want
> > wxlua_msw28d_wxbind.lib  Renamed to wxmsw28d_wxbind.lib.

Yes, but I like wxmsw28d_wxlua_wxbind.lib

> > In the last  i see now wxlua, this is why we once decide to use wxlua_
> > as a sort of name space.
> > I am not sure why wxCode prefers it different.
> it's not a preference - just a "bug". Definitively the <wxlike-lib> tag
> should take in account a prefix as other wxlike-* tags do.

Maybe an additional <wxlike-prefix-lib> that has the prefix could be
added. The <wxlike-lib> code is pretty small so it might not be too
much bloat. See below, that idea sounds pretty good and very simple.

> > Anyway it seems that all contrib stuff is in the from wxmsw28_nameofcontrib.
> > So looking at it like that maybe we should have:
> >
> > wxmsw28d_wxlua_lua.lib
> > wxmsw28d_wxlua_bind.lib
> > wxmsw28d_wxlua_debug.lib
> > wxmsw28d_wxlua_socket.lib
> > etc.
> hmmm, I don't see any great advantage over current naming, except that
> this is backward-incompatible for all ours wxLua users which should
> probably need to update their makefiles/project files without any real
> need (wxlike-lib tag must be fixed, not our naming rules).

I don't think we have to worry about backwards compatibility too much.
We have a small user base and hopefully things will be settled once
and for all after this.

I DO like this idea and think it's just as well. I'd keep the wx in
the second name though to be clear about what the lib is really for
since wxluadebug/socket are not generic debug/socket libs, but only
work with wxlua.

wxlua_msw26d_wxlua_lua.lib
wxlua_msw26d_wxlua_wxbind.lib
wxlua_msw26d_wxlua_wxbindstc.lib
wxlua_msw26d_wxlua_wxlua.lib
wxlua_msw26d_wxlua_wxluadebug.lib
wxlua_msw26d_wxlua_wxluasocket.lib

In any case, do whatever you think is best Francesco.

Was there anything else I've missed?

Thanks,
    John Labenski

ps. The precompiled headers are GREAT! I can't really tell much of a
difference in MSVC6, but I was thinking about how we could do it and
wanted to ask if you knew how, but thought it might be too much work.