[Qbs] External Dependencies

Иван Комиссаров abbapoh at gmail.com
Tue May 14 22:32:39 CEST 2019


> On Tue, May 14, 2019 at 11:09 PM NIkolai Marchenko <enmarantispam at gmail.com <mailto:enmarantispam at gmail.com>> wrote:
> Wouldn't it be more reasonable to implement something like OptionalDepends where you could just list all possible dependencies in the order in which it should be loaded?
> 

This doesn’t solve the problem of the boilerplate code, you're suggesting to add some syntax sugar.

However, it might be useful to specify the order in which probes/pkg-config/whatever are used (or even disable one of them).

Maybe, this can be done via product/module properties, something like

products.MyProduct.pkgconfig.condition:false

There are some corner cases when you’re searching for libs A and B and you want to use pkg-config for lib A and probes for lib B… Not sure if it’s worth supporting that case.

> 14 мая 2019 г., в 22:14, NIkolai Marchenko <enmarantispam at gmail.com> написал(а):
> 
> And while we are on the subject of finding libs. Is it possible to somehow indicate that a library you are trying to link isn't compatible with the compiler? Somethe _other_ than "unresolved external" error that can indicate anything from lib not being where you want it to be, a mistype in the path, incorrect lib version or, indeed, binary incompatibility. .
> 

For pkg-config, I don’t see such feature; it assumes that you’re set up paths so it won’t find wrong lib (paths like sysroot).

For Qbs itself, LibraryProbe should check for the desired architecture and discard incompatible libraries. I don’t see any problems implementing this.
It should also have a property to be able to choose between static/dynamic libraries. It’s quite dumb for now, actually=)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qbs/attachments/20190514/84478379/attachment.html>


More information about the Qbs mailing list