Hi,
It seems, I am sharing code across the projects wrongly: list of linked projects grows too fast in solutions. I read everything about code sharing and libraries I found in docs, however I can’t say surely that I get it right.
For instance, I am creating a little class library which has base class and few children – each child for particular device only. So in a particular project I need one child only. In order to achieve it, I create a library for a base class and library project per a child.
So in order to use a child class in a project, I need to add two library project into the main one: base library project and child library project.
So far so good.
But what if I need to make an extended version of a child? Currently I create another library project (grandson) where I put a grandson class only. Now I need to add 3 library projects to the main project. 
I’m afraid, that with such a technique my project will be bloated very soon what will definitely affect the compilation performance. Moreover, it’s cumbersome to add long list of libraries to the main project and it’s extremely difficult to maintain all over the projects.
So what is the best way to maintain hierarchical class library using vMicro?

I was tried to stop using code sharing library projects at all. But I couldn’t make the compiler see ancestor’s headers in a right place.

Tim@Visual Micro wrote on Oct 9^th, 2018 at 4:22pm:


I would gladly stopped using libraries if I knew another way of sharing own code.
Is there?