On Fri, 7 Jul 2006 17:00:11 +0200 (Romance Daylight Time)
Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>
>
> On Fri, 7 Jul 2006, Graeme Geldenhuys wrote:
>
> >> Packages exist 'on top of' the LCL. Widgetsets are 'under' the LCL.
Maybe right, maybe wrong.
There is the abstract LCL interface (interfacebase.pp, widgetset/*,
lclintf.pp)
which is used by the LCL
which is used by the LCL interface (gtk, win32, carbon, qt, ...)
So, an actual LCL interface is above the LCL.
> >>
> >> Michael.
> >
> > Ok, that makes sense, but I am still not sure where it should go...
> > When you compile the IDE, how does it know where to find things like
> > the CodeTools, etc..
The Makefiles contain the path to the codetools.
And they contain the path to the LCL.
The path to the current LCL interface is calculated with the environment
variable LCL_PLATFORM. Default is 'win32' for windows and 'gtk' for all
other.
> > For now, I am going to create symlinks to my actual code, but that
> > will obviously not work for Windows. It is just so I can continue
> > working for now.
>
> Careful:
>
> The lcl/interfaces/widgetset code should only contain the 'glue' code
> between the LCL and your widget set. The actual widget set can be in
> the FPC packages or any other directory.
Right.
To let the IDE find the sources (find declaration) you can do the following:
Create a package for your widgetset.
Create a package for the 'graeme' LCL interface.
Add the interface to the IDE units.
I can do that. I just need a name.
Mattias
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
