> If there is a better structure or overall approach I'm happy to > transitive includes and defines, but I do not want the transitive link > objects already compiled into a static library). > pulling in the CPP and H file into the test target and building them > containing the class or set of classes to be tested, I am manually > target for the test and then adding a link dependency on the library > The reason I'm asking this question is because of how I handle unit > Thanks, I will go through this and see if it helps. > just need to be copied into /usr/include. > and have all includes relative to that directory. > the project rooted in a single include directory in the source tree > The approach I use for include directories is to have all includes for > problems relating to the way you have your project header files > it is necessary for you to do this it sounds like you have bigger > I don't know of a way of doing it without target_link_libraries but if > happens under certain conditions (when using PUBLIC or INTERFACE > As you mentioned include directories do propagate but this only > directories between targets rather anything to do recursively handling > I presume recursively you mean propagating the required include Target_include_directories(Depender PRIVATEĭtto for other INTERFACE_.
#CMAKE INCLUDE DIRECTORIES RECURSIVE GENERATOR#
Properties explicitly with generator expressions.
I haven't tested this, but it should be possible to drag in the interface > link the libs I only want the include directories. > when passing targets to target_link_libraries(), but I do not want to > a target or set of targets? I know that include directories propagate > Is there a way to only take (recursively) the include directiories from > On 17 June 2015 at 12:28, Robert Dailey Next message: Recursively include target include directories only.Previous message: Recursively include target include directories only.Recursively include target include directories only Petr Kmoch petr.kmoch at (Again, this component only has one source dir but you can put a list of multiple source directory paths here and it will work.Recursively include target include directories only We do this for our internal unit test components: CMake will use globbing to find all the source files. This can be confusing if you share the codebase with multiple people.ĭespite all this, it is still possible to give a list SRC_DIRS instead of SRCS - similar to the GNU Make build system. The reason for encouraging "source files not directories" is that CMake only re-runs when it is necessary, and if you add a new file to the build when using globbing then CMake will not automatically re-run - CMake needs to be run manually then, or "idf.py reconfigure" needs to be run. If you're updating, you only need one CMakeLists.txt file in each place that you had a component.mk file in the old build system. (Note this uses a CMake variable called "srcs", this is optional you can also just list all of the source file relative paths one by one after SRCS. In ESP-IDF build system, this means passing them in by the "SRCS" parameter of idf_component_register. They can all be given in a single CMakeLists.txt file, even when the files are in multiple subdirectories, but CMake recommends listing each file name individually and not using "globbing" techniques like "*".
The "recommended CMake Way" is to list all of the source files by name.
0 kommentar(er)
