Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
7 years, 5 months ago.
what's the appropriate library dependency policy?
If I have
LibC as a common library that LibA and LibB depend on then what's the appropriate way to include libraries?
what's the appropriate dependency structure at application level.
I can see 2 models:
Flat Dependency Structure:
app
- LibA
- LibB
- LibC
correct dependency structure:
app
- LibA
- - LibC
- LibB
- - LibC
- LibC (if app uses it as well)
The correct structure seems to import the same library more than once. I am not sure if this is even going to compile.
So, it seems that the safest approach is a flat model.
What's the idiomatic solution?
Be the first to answer this question.