This is enough for my purposes in my workflow for the moment. Export the static library and its dependencies transitivelyīy “transitive,” I mean that if I import LibA in my project, and LibB is a dependency of LibA, then LibB will be automatically included in my project as well.Import third party libraries and their dependencies transitively.Link the source code into an executable.Compile source code into a static library.Success…?Īfter many days of reading documentation, debugging, and frustration, I was able to make this project template that is able to do 90% of the things I want: My Franken-Makefile was starting to look very appealing again. It seemed that the more that I read about CMake, the more confused I became.Įven worse, it became apparent that the “bells and whistles” are actually strictly required to get a project up and running. I (naively) figured that I could get a baseline CMakeLists.txt working quickly in order to continue working on projects as I slowly added all the fancy CMake bells and whistles that I had heard so much about. I eventually got fed up and decided to convert my active projects to CMake. I grew tired of slowly constructing a Franken-Makefile for each of my C++ projects and their dependencies for each machine that I use.Įach one was messy, bug-prone, and full of machine- and OS-dependent conditionals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |