[Lazarus] Different packages for different usage

Sven Barth pascaldragon at googlemail.com
Fri Jun 19 07:31:59 CEST 2015


On 18.06.2015 23:48, aradeonas wrote:
> Hi,
> I made package including some units that some of them need LCL but some
> of them will be need in server tools and they should not use LCL or
> graphical stuff so I want to make 2 package one for client app and other
> one for server with some of tools and without any dependency on
> graphical stuff so for server apps I will add server package.
> But I have units share with these two package that used TPicture in some
> parts but they can be removed with compiler condition.
> I want to know what is the best way to declare these two package and
> compiler condition so I will have two package with shared units but for
> different usage case.

In my opinion the best approach would be to put the shared units into 
their own package and have the code of those units /really/ be shared. 
This means no compiler defines that influence its behavior. And then the 
server and the client package depend on that package.

Regards,
Sven





More information about the Lazarus mailing list