I'd like to start a new thread to collect a list of scenarios and assumptions for consuming modules

Suppose we have:
Library A: contains Module A
Library B: contains Module B which imports Module A
Code C: imports Module B

Scenarios and assumptions:


  1. Main build of C.

1.1 The build needs to have Module B's and Module A's BMIs to be able to compile the source using it.

The build needs to either

1.1.1. find BMIs (assuming it can read them)

or

1.1.2. somehow build the BMIs (assuming it cannot read them).

1.2. The build also needs to find and link static lib of Library B (which contains implementation of Module B), as well as static lib of Library A (which contains implementation of Module A).


  1. Tools outside of the main build (IDE, static analysis, etc.) need to compile/parse C.

Assumption: the main build of C succeeds on the same machine.

For that they need to be able to rebuild Module A and Module B (the assumption is that they never can read BMIs).

Does this sound right and are there any other scenarios/assumptions?

Thanks,
Olga