| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I3c9e5d5512cad7028026d6166a0783fd507e7826
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This decouples building and installing, e.g. allowing
the latter to be executed by a privileged user
to a system-wide directory.
In addition, the ability to install build artifacts
(typically executables or libraries) has been added.
Change-Id: I28e725e4c1168eebe88e12c75e3d3e9f5fe28ca5
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
The problem is that files matched by an "install" rule are currently not
added to the target artifacts if a build graph already exists and they
are "implicitly added" by adding or renaming a file in a group matched
by a wildcard (i.e. the change happens without touching the project
file).
Task-number: QBS-146
Change-Id: Iec499de8dd88e3ac599b7435ec441aad7689f55a
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|