[QBS] How to specify dependency outside of the project heirarchy?

Joerg Bornemann joerg.bornemann at nokia.com
Mon Mar 19 16:51:09 CET 2012

On 16/03/2012 18:06, ext devtomsci at me.com wrote:

> I was also getting confused by the fact I needed:
> moduleSearchPaths:"x"
> ./x
> ./x/LibFoo/
> ./x/LibFoo/nameNotImportant.qbs
> Rather than just:
> ./x/LibFoo.qbs
> Is there a reason we can't support the second form as well? It makes my
> project structure slightly neater, although it's not a major issue.

AFAICS there's not a strong reason against this explicit form of 
specifying a dependency.

>  > The grammar is in <qbs-repo>/src/lib/parser/qmljs.g
> Yikes :) Looking some more in that area, I think
> Loader::setupInternalPrototype() in QBS/src/lib/language/loader.cpp is
> more what I was after - a definition of all the properties you can set
> in the different block types.

Ah that's what you mean. :-)
Yeah that's the central place where the internal types are registered.

> FWIW my 50 file + 3 external libraries project is now fully building
> from qbs :-) Had to hard-code some paths and make some workarounds due
> to bugs or missing features (QBS-64, QBS-52, QBS-83, QBS-75, QBS-82, at
> a quick approx) but on the whole it's looking very good and my qbs and
> qbp files are way neater than their qmake equivalents :)

Nice to hear! :)



More information about the Qbs mailing list