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

Dependency matching should be less strict when multiplexing

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Done
    • Not Evaluated
    • 1.16.0
    • None
    • Dependency Tracking
    • None

    Description

      The following scenario is currently not allowed, but it should:

      Project {
              Product {
                  name: "multiplex-without-aggregator-2"
                  multiplexByQbsProperties: ["architectures"]
                  qbs.architectures: ["TRS-80", "C64"]
              }
              Product {
                  name: "multiplex-without-aggregator-4-depends-2"
                  multiplexByQbsProperties: ["architectures", "buildVariants"]
                  qbs.architectures: ["TRS-80", "C64"]
                  qbs.buildVariants: ["debug", "release"]
                  Depends { name: "multiplex-without-aggregator-2" }
              }
      }
      

      Suggested algorithm if both product and dependency are multiplexed:

        - if candidate with identical multiplex id exists
          - take this, ignore all others
        - else if intersection of multiplex properties between product and all candidates results in single match
          - accept it as the result is unambiguous
        - else if no match
          - error "no eligible multiplex candidate"
        - else if multiple matches
          - error "ambiguous dependency"
      

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            rweickelt Richard Weickelt
            rweickelt Richard Weickelt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes