For my research, I've developed a C++ command-line library that contains several classes, each with a .h header file and a .cpp implementation file. For each new project using the library, I have to copy both files for every class into the project and make each .cpp a build target. Then in the program I actually want to use the libraries in I #include "all.h" (where all.h is just a single master file that includes all the headers of the library).
This is not ideal. I would like to be able to #include <stuff/all.h> where I can have a separate project for just the library which I can edit and build, and then any other projects using it would build using the appropriate object files. I would imagine this would be done either through a Framework or symbolic links, but I really have no idea. Can anyone help with this matter?
This is not ideal. I would like to be able to #include <stuff/all.h> where I can have a separate project for just the library which I can edit and build, and then any other projects using it would build using the appropriate object files. I would imagine this would be done either through a Framework or symbolic links, but I really have no idea. Can anyone help with this matter?