How to properly organize the storage structure and version control of the project?

Question

git

Hello!

I am engaged in the optimization of development processes, as well as the introduction of CI / CD practices, I use gitlab and its auto-assembly system, I have a project in development (qt, C ++, but I think this is not important), using libraries, which in fact are also separate subprojects that implement certain functionality, without them the main project does not work and is not going to!

How to properly organize the storage and assembly of projects and subprojects, should the sources for building libraries be in separate repositories, now everything is stored in one heap - separate compilation allows you not to rebuild the project completely, but it seems to me that it’s right to scatter subprojects across different repositories and build them separately, there is the main project is the libraries, for each one you can separately create a repository and implement version control, autotests, plus it’s convenient to keep labor costs and track changes, because now the devil will break his leg there?

Write about your practice of managing and organizing projects!

Thanks to all who answered.

Answer 1

If the situation is "a bunch of libs (dll) and one project", then I do this for myself:
For each lib, a separate repository, such a lib does not know in which projects it will be used, it simply issues its dlls by version, who wants which version - this one takes
Projects that use these libs store them in their libs folder
It turns out:
1) You create a project
2) Take the necessary libs and copy their dlls directly to the project folder (I personally don’t like it when a project starts getting every time either unknown from where, sources may die or change)
3) Done
The system is the same as if these libs were not yours, but from a third-party developer. Such developers sometimes have repositories, and there are ready-made dlls. How do you proceed in such a case? Connect the repository and compile? Are you just copying the dll into the project? Do the same with your libs
In visual studio, by the way, there are so-called "solutions" that put projects together and compile them