[build2] Using build2 on a project with lots of dependencies

[Klaim - Joël Lamotte]

On 20 December 2017 at 18:00, Philippe Payant <philtherobot at gmail.com>
wrote:

> I understand that build2's take is that dependencies should be source, not
> binary.  You have your project, and the dependencies are installed as
> packages, which implies that all the dependencies are built with build2.
> Did I get this right so far?
>
> There are great reasons to depending on sources and compiling them
> according to the correct configuration - no problem here.
>
> My project depends around 20 libraries and... on Qt.  Obviously, right
> there, compiling Qt on each configuration is a no-go, and Qt does not build
> with build2.
>
> This is so obviously wrong, I am sure there is something I do not
> understand.  Something I missed after reading the FAQ, the build2 manual
> and watching the CppCon talk.  Anyone can explain?
>
> In any case, what I would like is to setup things such that all those
> dependencies are prebuilt and shared amongst my configurations.  I am ready
> to run the risk of a configuration/library mismatch and manage this
> myself.  I get reduced disk usage and faster compilation times in
> exchange.  The build2 configuration directory is hackable, so maybe there
> is a possibility through there.
>
> --
> Philippe
>

Well the FAQ presently says "Not at this early stage but maybe in the
future." and follows on,
but I suspect that it is indeed simply inevitable to at least allow users
to define packages which contain binaries
and let them describe where the "interfaces" to these binaries are
(headers, modules, libs etc).

So it will very probably happen. But I don't expect this to come soon.
Except if modules + some big tooling revolution change le C++ landscape
forever, of course, but it's not highly probable.

A Joël Lamotte
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/users/attachments/20171220/2b62c2ec/attachment-0001.html>