[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]

RE: [XaraXtreme-dev] includes, XARLIB and camtypes.h

That's more like it.  That updated a lot of the files in XarLib and now
there are build problems...

I should be able to sort them out fairly easily but they mostly seem to
be caused by include spaghetti (e.g. camresource.cpp needs ccfile.h so
that it will compile but that is currently included via camfiltr.h (and
possibly other things) that isn't part of XarLib.  I should be able to
sort this out by explicitly including files like ccfile.h directly in
camtypes.h rather than relying on another header to pull them in.
Presumably then your removal script can be run again to remove ccfile.h
from all the other places it gets included.

To help this, is there an easy way (presumably using one of your
scripts) to tell how a particular header file is being included?


-----Original Message-----
From: owner-dev@xxxxxxxxxxxxxxxx [mailto:owner-dev@xxxxxxxxxxxxxxxx] On
Behalf Of Alex Bligh
Sent: 09 June 2006 10:42
To: dev@xxxxxxxxxxxxxx
Cc: Alex Bligh
Subject: RE: [XaraXtreme-dev] includes, XARLIB and camtypes.h

--On 09 June 2006 10:38 +0100 Gerry Iles <GerryI@xxxxxxxx> wrote:

> Incidentally, I believe the only files you've changed that are part of
> XarLib are camtypes.h and errors.cpp and simply moving the include of
> paldefs.h to inside the conditional (as it is not a part of XarLib)
> allows it to compile a release build ok.  I'm just testing the debug
> build but I don't anticipate any further problems...

OK. But I haven't done the monster include removal checkin yet. I will
do it right now.