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

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

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.

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. I understand for one lib 
project there is no confusion.
But for project with several modules, i don't like it. Like in wxArt2d i 
have 16 libraries coming from 16 modules.
If there is no name space at the start like wxart2d_mswd28d_curves.lib 
wxart2d_mswd28d_kbool.lib etc. i think it will be harder to find out 
what library comes from what after installation.
Looking at  the wxWidgets naming , i also see  wxbase28.lib, next to 
wxmsw28_core and wxmsw28_stc, i don't see the logic.
I only see "wx" as common namespace, why did they not use wxmsw in front 
of all??
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.

or if oke:

wxmsw28d_lua_lua.lib
wxmsw28d_lua_bind.lib
wxmsw28d_lua_debug.lib
wxmsw28d_lua_socket.lib

In the end for wxstedit, it is not:

wxmsw28d_wxstedit.lib

but:

wxmsw28d_stedit.lib

So only one time the wx in it.
Like:

wxnamespace+platform+version_libraryset_specificModule.lib

What do we think is best?

Klaas