[QBS] Absolute paths in Product.destination question

Christian Kandeler christian.kandeler at digia.com
Fri Mar 8 11:27:56 CET 2013

On 03/08/2013 05:12 AM, Smirnov Vladimir wrote:
> First: according to https://bugreports.qt-project.org/browse/QBS-116 ,
> in QBS ideology we shouldn't have output artifacts outside build dir.
> When we build application, it should moved to dest using install comand.
> Okay.
> Just imagine (real for me) situation:
> we have large project with some static libraries and end-applications.
> -static_A.lib
> -static_B.lib
> -static_C.lib (depends on A and B)
> -binary_X.exe
> -binary_Z.exe (depends on all static libs, uses them as input)
> (In real amount is larger. About 20 libs, but they all have typical
> rules of build, so qbs configs is cute =) )
> When linking wnd-apps, linker expects all static libs (not only these in
> project) in certain absolute dir. It can be made relative, but it
> obviously higher that any of used build-dirs.

This sounds weird. Are you saying the linker does not let you specify 
paths to libraries?

> I could create install command, for each of these static library, but
> when i execute "qbs build" command for end-apps, they will use the old
> ".lib" files.
> And if i use "qbs install" command, end-apps will be compiled BEFORE
> install commands move compiled libs to expected folder, won't they?
> So, what is ideologically right way to organize easy build "in one
> click" without building libs and apps in two steps?

If the app and the lib are in the same project, then qbs knows where the 
lib is when linking the app, so installation of the lib is not part of 
that process.


More information about the Qbs mailing list