[Wxlua-users] Directory structure (was Re: wxlua.sourceforge.net is opened)

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

> >1) Create libs for each of these bindings, but we might have quite a
> >few of them.
> =20
> Right, that is the idea.  One can of course combine small things in one l=
ib.

We need to make it so that you can have a fine control over what
wrappers get linked to your library, see the wxLUA_USE_XXX defines in
luasetup.h, there are over 100 of them. Take the printing wrappers as
an example, an embedded program might want to exclude it, but the
wxLua program wants it. I'm going to be building both types of
programs and I want to be able to do so without any special effort.

> >    Use some sort of luasetup.h (equivalent  to wxWidgets/include/msw/se=
tup0.h)
> >    I cannot think of any way to get the lib to be compiled using a
> >user"s luasetup.h file
> >    without making people edit things by hand. I think this is unworkabl=
e.
>
> Francesco is generating by bakefile inside the makefile a   art2dsetup.h =
.
> Here all option are defined. Evetually there will be a program to easily=
=20
> set the options.
> Is this what you mean??

Things that we should avoid:=20
1) Making people have to edit files that will be overwritten by a new
cvs update.
2) Making people have to edit files when they switch between compiling
wxLua and their own project, both should work at the same time.

> >2) Make the "end user" compile each cpp binding into their project by
> >hand selecting them.

> wxArt2d has wrapping, it first automatically the wxLua wraps, next art2d=
=20
> module luawraps, next the application extra wraps
> There must be a means to automate this. I did it with Cmake. But i think=
=20
> bakefile can handle it too.
> And else we might simple use Unix scripting (MSYS on windows ).

I just use .bat and BASH shell scripts, it works well.=20

=3D=3D=3D=3D=3D=3D=3D=3D

I'd like to hear what Ray and Paul think of either of these two
methods and the dir structure.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Ok, back to the dir structure (but getting a handle on the above might
make this more clear too)

My only concern with the modules dir is that there are a going to be
lot of nearly empty dirs that will make navigating it a little
cumbersome.

Do the "modules" dir get "docs, bin, build" and what not too?

Hows this?=20

wxLua/
    art/           - all images go here, preferably in XPM format
    bin/          - output binaries go here, lua for example
    build/       - cmake, bakefile stuff here
    docs/       - any generic docs go here
    include/wxlua/  - REMOVE THIS?
    lib/                - output libs go here, wxlualib for example
    thirdparty/
        lua/                - lua itself=20
            include/
            src/
            ...
    modules/
        wxluacore/  -- was "Library" (BUILT AS LIB TO wxLua/lib)
            include/
            src/
        wxluasocket/  -- parts of "Library" that are for sockets make
this a lib too
            include/         (BUILT AS LIB TO wxLua/lib)
            src/
        wxwidgets/
            (No include since no public headers)
            src/        wxLuaPrinting.h/cpp, wxLuaHtml.h/cpp go here
(HOW TO COMPILE?)
            build/     (if needed ??)
            import/  -- was "Import" (WHERE DO BINDINGS GET BUILT TO?)
            bindings/  -- (PUT BINDINGS HERE?)
        bit/ - there's a lua bitwise library which might be nice
            src/  =20
        wxtreelistctrl/  -- (for example, I don't personally need this...)
            import/   -- assume that the person put wxTreeListCtrl on
same dir level as wxLua
    apps/    ?or programs?
        wxlua/              - the "Standalone" program
        embedded/
    src/                - REMOVE THIS?
    samples/            - "Examples"
        samplename/     - any multifile sample should get its own dir
    utils/              - generic utils, bin2c for example

Regards,
    John Labenski