#Cmake install multiple files how to#
#Cmake install multiple files generator#

In the following, I will use the NUCLEO-F413ZH demo board (which costs about 25 в‚¬). Another good reason is because ST provides cheap and efficient demo boards.

I have been using MCUs from this family for years now, which is a good reason to use them here. STM32 is a family of 32-bit processors by ST-Microelectronics, based on ARM Cortex-M designs. CMake is by far the most widely used build system in the C++ world, and better integration with it is sorely needed. It is becoming so popular that it will probably be the build tool for Qt6:ДЇor Qt 6, we aim to use CMake as a standard 3rd party build system to build Qt itself. In fact, it is more about CMake on MCUs but I had to pick one for the examples.Д¬Make is becoming the de-facto standard tool to build C and C++ projects.

#Cmake install multiple files generator#

Also, one cool thing is the DEPENDS part in the macro also lists the generator script.This article is the first of a series dealing with CMake and STM32 microcontrollers. I also specified INSTALLs for the output files. I chose to use the filename of the output file as the name of the target. The macro is more general, and in the foreach, I use it in a specific way. macro(add_some_kind_of_target target_name infile outfile)Д¬OMMAND my_script.sh -in $ DESTINATION share/sqlite/database/BD) One could create such an add_macro for each command that they use to generate things. Given our situation, you may modify the generated file and see how that goes, then if pleased, you modify the input file.ДЄ macro called add_something that creates a target. I applied it to one situations where the files are all generated the same way but updating one of the dependencies would cause the whole group of files to be regenerated. I've used your thing in many places with different files and different commands. They were not in the same directory which is why I couldn't get it to work (I think) but either way, the way he's doing seems to be the 'right' way. Just a simple script generates an output file from an input and I couldn't get making the target to cause the script to be called to generate the files. Oh and as for 'can I get that somehow?', the answer seems to be yes, but I was trying that at first and could not for the life of me get it to work. ДЄ target created in the same directory (CMakeLists.txt file) that specifies any output of the custom command as a source file is given a rule to generate the file using the command at build time.Д«ut goes on to say not to do that if you have multiple targets that depend on one of those files.Дo not list the output in more than one independent target that may build in parallel or the two instances of the rule may conflict (instead use the add_custom_target() command to drive the command and make the other targets depend on that one).ДЇrom that my takeaway is that I will always create a target and not have other targets depend directly on the files.

The documentation seems to say at first that you could do that. That's it that's all for those files and how and when to generate them.ДЄfter that I should be able to say that some target depends on that file and CMake should know what to do.

#Cmake install multiple files how to#

That's what I wanted to do and what seemed the most straightforward way of doing things: 'Hey CMake, here is a group of files and here is the group of files they depend on, and here is how to generate them. In my project I'd like to just have the foo target and not the libfoo_untar target.