-
Bug
-
Resolution: Done
-
P2: Important
-
1.8.1
-
None
-
9ecc36e2eb1f8e12cf6537cad40acbf3890ed156, 7e630a14369d30d7658ebda34ac6233ec1be1a2e
Acc. to my experience it looks like that the Export section of a disabled component (i.e. the condition for that component evaluates to false) is still enabled and has to disabled explicitly, too.
So situation is like:
...
Product {
name: "test_without_explicit_Export_condition"
condition: false
Export {
Depends { name: "cpp" }
cpp.includePaths: { throw "Should not throw but does" }
...
}
...
}
My current workaround is
...
Product {
name: "with_explicit_Export_condition"
condition: false
Export {
condition: product.condition
...
}
...
}
I'm not really sure whether to classify that as a bug but at least it is not what one would expect.