delta/qbs.git/src/lib/buildgraph/tst_buildgraph.cpp, branch dynablaster

Some minor improvements to the Error class.

2013-06-18T08:57:25+00:00

- Rename "Error" to "ErrorInfo", to make clear that this class conveys
information about errors, including that there might not actually be
one.
- Rename "ErrorData" to "ErrorItem", to make clear that these are parts
of an aggregate structure.
- Introduce ErrorInfo::hasError() for quick checking of whether an error
occurred.

Change-Id: Icea6ed5240d6d14bd30e9cea189c6babd7004792
Reviewed-by: Joerg Bornemann

Remove structural redundancy in project and product classes.

2013-04-12T12:19:12+00:00

We had two project classes, each holding a list of products
that was structurally identical, except that no BuildProduct
object existed for a disabled ResolvedProduct. The same kind
of duplication also happened for product dependencies.
This patch gets rid of these parallel structures. BuildProject
and BuildProduct are largely being demoted to data holders and are
aggregated by ResolvedProject and ResolvedProduct, respectively.
The resulting project structure should be easier to understand
and maintain.

Change-Id: I68beef60b9e0d62258f6a8337c9015864e18bd80
Reviewed-by: Joerg Bornemann

Build a shared library.

2013-02-08T16:29:16+00:00

We don't want our code to be duplicated in memory for each application
that uses it, so the library should not be linked statically.
Some ramifications worth mentioning:
    - The unit tests had to be moved into the library,
      because otherwise we would need to export random
      internal symbols. This is why the patch appears so big.
      A follow-up patch should probably make compilation
      of tests optional, so the library can be deployed without
      unneeded code.
    - The DESTDIR of the auto test executables is now the
      same as the one of all other executables, so they
      can all use the dll on Windows without additional
      setup.
    - Some internal symbols were exported, namely:
          a) Logging-related stuff. This allows us to use
             a uniform logging approach in the library and in
             our command-line tools; I consider this acceptable.
          b) A handful of classes and functions currently needed
             by certain command-line tools. These seem more questionable
             to me and we should probably find a different way to implement
             the respective functionality.

Change-Id: I9cd21e12cd622b55cf62f5e04ad398734410ede1
Reviewed-by: Joerg Bornemann