<html><head></head><body bgcolor="#ffffff" text="#2e3436" link="#2a76c6" vlink="#2e3436"><div>Hi Paul,</div><div><br></div><div><span><pre><pre>On Mon, 2018-11-12 at 20:44 +0100, Paul Gevers wrote:</pre></pre></span></div><blockquote type="cite"><pre>Dear all,
I assume you noticed that I uploaded the release candidates of lazarus
</pre></blockquote><div>That's a great news, thanks for your effort.</div><div><br></div><blockquote type="cite"><pre>recently. In my last upload, I revisited the autopkgetest that we (I)
have added to the package. While going through some of the (currently
accepted) failures, I was wondering what it means if package A depends
on package B, both are available, but not compiled by default. It seems
</pre></blockquote><div>Can you please explain this a bit more? Do you mean that these packages are not compiled by the make file upon build of lazarus?</div><div><br></div><blockquote type="cite"><pre>that $(lazbuild A) fails to find (and) compile package B, even if
package B was compiled just before. It seems the logic of lazbuild
</pre></blockquote><div>So you compiled package B and then try to compile package A that depends on B, isn't it?</div><div>Did you install the package B first? Please refer to --add-package command line option of lazbuild.</div><div><br></div><blockquote type="cite"><pre>should grow some "please also look into the $HOME/.lazarus/ folder for
the compiled units".
</pre></blockquote><div>Normally the primary config path is set to this path. So Idon't think we need to change anything for that to work. I assume it is only a matter of installing the packages using --add-package</div><blockquote type="cite"><pre>
Did I conclude this correctly? Is this already supposed to work? Should
we report this upstream?
</pre></blockquote><div>Let's first conclude there is a bug then we can try to contact them, but recently they didn't help too much. They don't seem to appreciate the split on multiple packages and they do distribute their own unique deb package.</div><blockquote type="cite"><pre>
It seems to me quite some of the current failures could be avoided and
leaves us with packages (e.g.) meant for Windows.<br></pre><pre></pre></blockquote><div>This is probably true.</div><div><div class="-x-evo-signature-wrapper" style="white-space: normal;"><span class="-x-evo-signature" id="1423923852.20958.6@karim"><pre><pre>-- <br></pre>Cheers,
Abou Al Montacir</pre></span></div></div></body></html>