Hi, this is a bit a tricky question and probably can't be really solved.
I have multiple libraries, each library has a project and is mostly self contained. There are some dependencies between the libraries but that is solved by using compiler variables. Each libraries lives in it's own git repository and it is intended to develop them mostly on their own.
I now want to create a "suite" that contains many libraries. To do that I would create a git repository with submodules that merge the different repos into one big one. (If you don't know what I am talking about, think I copied the folders all together.) I would then create one workspace that contains all the projects. By adding project dependencies I fix the build order, what is really nice. But here is my actual problem, in this case I want the libraries to link from the recently built libraries. To do that I have to change the include and lib path to point to the relative path, BUT I still want each library to be buildable on it's own.
Any ideas how I can solve this duality?
One idea I have is to have both relative and compiler variable path in the include and lib path and hope it turns out well. But I can imagine many ways how this could break. There must be a more elegant solution, like employment a build script, but I can't wrap my mind around it.
