> i'm trying now to set the library in cpp.staticLibraries or directly the
> full path to the .a as a cpp.linkerFlags but the project won't detect if
> the library has changed.
Shouldn't you use cpp.libraryPaths instead of cpp.linkerFlags?
> if i modify the library and recompile it, then run the
i'm trying now to set the library in cpp.staticLibraries or directly the
full path to the .a as a cpp.linkerFlags but the project won't detect if
the library has changed.
if i modify the library and recompile it, then run the project it will
just run as if nothing had changed, it won't link the ne
Yes i already have a module that exports all the search paths and other
flags common to the library and applications using it.
To explain better the use case, the library i develop has around 200
examples, every time a user wants to compile one the library has to be
compiled already otherwise havi
> I develop an open source library which i also use in my projects. I have
> created a qbs project for my applications that has the library's qbs as
> a dependency, using reference. The problem is that whenever i start a
> new application it recompiles the library completely.
>
> Instead of recompi
Hi
I develop an open source library which i also use in my projects. I have
created a qbs project for my applications that has the library's qbs as
a dependency, using reference. The problem is that whenever i start a
new application it recompiles the library completely.
Instead of recompiling ev