On Sat, Jul 20, 2019 at 6:24 AM Mattias Gaertner via lazarus
wrote:
>
> On Fri, 19 Jul 2019 00:26:49 -0300
> "Marcos Douglas B. Santos via lazarus"
> wrote:
>
> > Hi,
> >
> > Imagine a package that has a dependency for another one. However, this
> > dependency has a conditional to exists. So, I c
On Fri, 19 Jul 2019 00:26:49 -0300
"Marcos Douglas B. Santos via lazarus"
wrote:
> Hi,
>
> Imagine a package that has a dependency for another one. However, this
> dependency has a conditional to exists. So, I cannot add the Required
> Package by default — I'm talking about ZeosLib.
>
> Then, I
On Fri, Jul 19, 2019 at 10:30 AM Tony Whyman via lazarus
wrote:
>
> My understanding is that when you add a "required package" what actually
> happens is that the IDE adds the package unit paths to the list of unit
> paths for your project, and adds the top level .pas file for the package
> (which
My understanding is that when you add a "required package" what actually
happens is that the IDE adds the package unit paths to the list of unit
paths for your project, and adds the top level .pas file for the package
(which usually has the same name as the package) to the "uses" clause in
your
Maybe adding "dynamically" the Required Package, rather using
"dynamically paths" by Conditionals, could fix this?
But how to do this?
Just to be more clear, I don't have any "Duplicate units" as compiler is saying!
Thanks.
regards,
Marcos Douglas
--
_
Hi,
Imagine a package that has a dependency for another one. However, this
dependency has a conditional to exists. So, I cannot add the Required
Package by default — I'm talking about ZeosLib.
Then, I used Conditionals (script) for adding ZeosLib paths (-Fu, -Fi)
into the paths of the package — a
