Uploaded image for project: 'Qbs ("Cubes")'
  1. Qbs ("Cubes")
  2. QBS-1517

List properties should be merged in reverse module dependency order

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Not Evaluated
    • Resolution: Done
    • Affects Version/s: 1.14.1
    • Fix Version/s: 1.16.0
    • Component/s: Dependency Tracking
    • Labels:
      None
    • Platform/s:
      All
    • Commits:
      8ff1dd0044a32b6658cf05a923946d75baf33a66 (qbs/qbs/master)

      Description

      Consider the following project:

      Module {
          name: "common"
          property stringList listProp
      }
      Module {
          name: "higher1"
          Depends { name: "common" }
          common.listProp: "higher1"
      }
      Module {
          name: "higher2"
          Depends { name: "higher1" }
          common.listProp: "higher2"
      }
      
      Product {
          name: "p"
          Depends { name: "higher2" }
          common.listProp: "product"
          property stringList showMeTheOrder: {
              console.info(common.listProp);
          }
      } 
      • Expected output of listprop: [product, higher2, higher1, common]
      • Actual order: [product, higher1, higher2, common]

      Looks like common is correctly placed at the end, but the order of higher1 and higher2 is incorrect.

      cpp.includePaths. Module dependency relationships should be respected. Ideally, the merge order should be controllable by a property in PropertyOptions.

        Attachments

          Issue Links

          For Gerrit Dashboard: QBS-1517
          # Subject Branch Project Status CR V

            Activity

              People

              Assignee:
              rweickelt Richard Weickelt
              Reporter:
              rweickelt Richard Weickelt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes