Topic: Units, interfaces and the relative ways
In addition to a question about who interests as solves the following question: we Have certain general Core1 unit and interfaces to it (.h.idl...) Product1 common core1 include (interfaces here) Product2 src components goodwork1 goodwork1 wants interfaces core1 (the Real situation certainly much worse. Any units of pieces so 100, and they from each other depend in a different level ) and. It is possible to refer to interfaces through the relative way.\.\.\Product1\common\core1\include Looks as a brothel. To reorganize core1 more difficult. It is possible to lay out interfaces in a separate place, both units refer to it Product1 interfaces common core1 include Product2 src components goodwork1 core1-.\.\interfaces goodwork1-.\.\.\Product1\interfaces\include In Product1\interfaces there is a heap interface . Similar on a brothel. TeamCity reacts on in all directory and rebuilds all dependent modules which look in Product1\interfaces even if interesting them did not change. c. It is possible to copy necessary interfaces and to demand from developers not to import breaking changes Product1 common core1 include (the freshest interfaces here) Product2 src components goodwork1 external core1 include (the copied interfaces which have probably become outdated) Breaking change of interfaces (and somebody, it is sometime mandatory them ...) will be noticeable only in .