wxlua-users

[Wxlua-users] wxluasetup.h include path

[k. h. <kla...@nl...>]

Hi,

We started with only one incldue path to "$(WXLUA_BASEDIR)/modules"

And use in our files this:

#include "wxlua/include/internal.h"

But now wxluasetup.h creaped in, and requires to add

$(WXLUA_BASEDIR)/modules/wxbind/setup

I wonder if this is wise?
Is they idea to have several wxluasetup.h files, reality?
I am not sure i  understand why it had to be in the wxbind module in the 
end, but if it is meant for that module, why not put it its include dir?
And include where needed as:

#include "wxbind/include/wxluasetup.h"

or next would be oke too i think.

#include "wxbind/setup/wxluasetup.h"

Like it is now, external librarues/apps need to set two include dirs 
again. And if there will be more wxluasetup.h files, the is the begining 
of more include paths.

So i suggest to remove the next as include path

$(WXLUA_BASEDIR)/modules/wxbind/setup
and use internal and external to wxLua:

#include "wxbind/setup/wxluasetup.h"

Of is it is in the end not so wxbind specific, make a setup dir within 
the modules directory and include wxluasetup.h from there.

#include "setup/wxluasetup.h"

regards,

Klaas

-- 
Unclassified

[Wxlua-users] Re: wxluasetup.h include path

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

Hi,

k. holwerda ha scritto:
> We started with only one incldue path to "$(WXLUA_BASEDIR)/modules"
right


> And use in our files this:
> 
> #include "wxlua/include/internal.h"
> 
> But now wxluasetup.h creaped in, and requires to add
> 
> $(WXLUA_BASEDIR)/modules/wxbind/setup
> 
> I wonder if this is wise?
> Is they idea to have several wxluasetup.h files, reality?
yes; if you go in wxLua/modules/wxbind/build and type

   nmake -fmakefile.vc WXLUASETUP_DIR=c:\mydir WXLUABINDLIB_DIR=c:\

then a wxbind library with your custom wxluasetup.h (which must be in 
c:\mydir) is created and put in c:\

> I am not sure i  understand why it had to be in the wxbind module in the 
> end, but if it is meant for that module, why not put it its include dir?
it's in wxbind/ and not directly in modules/ because it regards wxbind 
module only.
And it's not in wxbind/include/ because that dir _must_ always be 
included. the official wxluasetup.h must be something which we can 
decide to include or to exclude at will (e.g. when building user's 
custom wxbind we still need to include wxbind/include folder but we do 
not include the wxbind/setup one; rather than we include the folder 
specified by WXLUASETUP_DIR).

If we keep wxluasetup.h in the wxbind/include then even if we add to 
include search paths WXLUASETUP_DIR we cannot be 100% sure that compiler 
will choose the wxluasetup.h found in WXLUASETUP_DIR rather than the one 
in wxbind/include...


> And include where needed as:
> 
> #include "wxbind/include/wxluasetup.h"
> 
> or next would be oke too i think.
> 
> #include "wxbind/setup/wxluasetup.h"
using this form we force the user to keep his custom wxluasetup.h in a 
setup/ subfolder...


> Like it is now, external librarues/apps need to set two include dirs 
> again. And if there will be more wxluasetup.h files, the is the begining 
> of more include paths.
well, wxlua & wxluaedit applications do not include wxluasetup.h; only 
wxLua modules (and wxLuaCan) do.

I thought it was possible to build wxLua applications (in C++) which do 
not include wxluasetup.h... is it right ?

Francesco

Re: [Wxlua-users] Re: wxluasetup.h include path

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

Francesco Montorsi wrote:

> I thought it was possible to build wxLua applications (in C++) which 
> do not include wxluasetup.h... is it right ? 

Oke i now understand all behind again.
I was under the impression wxluasetup.h was always needed.
But i am not sure.

Klaas

Re: [Wxlua-users] Re: wxluasetup.h include path

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

On 2/6/06, klaas.holwerda <kho...@xs...> wrote:
> Francesco Montorsi wrote:
>
> > I thought it was possible to build wxLua applications (in C++) which
> > do not include wxluasetup.h... is it right ?
>
> Oke i now understand all behind again.
> I was under the impression wxluasetup.h was always needed.
> But i am not sure.

I thought I removed the
#include "wxbind/setup/wxluasetup.h"
from wxLuaCan? It's not necessary unless in C++ you want to know what
parts of wxWidgets you've got.

Only modules/wxbind should ever care about wxluasetup.h.

-John Labenski