Thanks for help, i've done some digging and understand my mistake, I now
tell it, if it helps somebody:
if we write Depends block, we dont need to owerwrite the absolute path
of the lib, qbs done all the work automatically (it suprising, but
non-intuitive)
StaticLibrary{
Depends { name: "cp
On 03/08/2013 01:36 PM, Smirnov Vladimir wrote:
> "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.
> "
>
> Is it right that even .lib file placed in temporarily build folder ,then in
>
"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.
"
Is it right that even .lib file placed in temporarily build folder ,then in
another product (app) build it (lib) will be passed to linke
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 fo
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
