NOTE: Put the code snippets before the add_subdirectory() call References You can always overwrite command behaviors: function(add_library _target) TARGET 'module' was not created in this directory. Use the cmake_policy command to set the policy and Policy CMP0040 is not set: The target in the TARGET signature ofĪdd_custom_command() must exist. You will get from CMake: CMake Warning (dev) at CMakeLists.txt:8 (add_custom_command): If you now just add to following to the root CMakeLists.txt: add_custom_command( Set_target_properties(module PROPERTIES WINDOWS_EXPORT_ALL_SYMBOLS 1) Moreover, In another approach I write a bash script file to copy the files and call it in major CMakeLists.txt via bellow command. I tried some other commands such as file (COPY ) and configure_file() but I think they operate in generating cmake-cache phase and just can copy resource files which are exist in pre-build phase. On the other hand it must done in outer(major) CMakeLists.txt which has others(libraries/modules).

I need to copy outputs of libraries/modules without changing their CMakeLists.txt ( add_custom_command with POST_BUILD option actually is not a good choice because at this point I need to change CMakeLists.txt of libraries/modules which they are not just belong to my project). They included in my project using add_subdirectory command (note that my project just made up from multiple modules and it has not any add_library or add_target).

I have a cmake project which has several libraries and modules. Folder of app1 must contain module1.dll and lib5.dll, app2 needs lib5.dll and finally app3 needs module1.dll(number of apps, modules and libs are more than this example and as I explain below we don't want to change modules/libraries's CMakeLists.txt, just main's CMakeLists.txt is ours). Which output of module1 is module1.dll and output of library5 is lib5.dll. This way, you can call make generate to just generate the message file or just make to build the whole project without having to call generate separately.Ĭhanges in your proto files will be picked up by the makefile and considered in your next build.As an example suppose four folders(app1, app2, app3 and main) such as below main You can do this simply by adding the generate target as a requirement for your debug, release, and all targets. The parameters to protoc ensure the Embedded Proto plugin is used, the required include folder is passed to protoc together with the output folder, and the *.proto file being processed is set. The calls to change the directory and protoc are on one line with ampersands otherwise, each call would be executed in its own shell rendering the change dir useless. Protoc is run from the Embedded Proto folder such that the plugin is found using relative paths. The implicit target makes sure the output folder exists, and it runs protoc. $(shell mkdir -p $(dir $(EMBEDDED_PROTO_DIR) & $(PROTOC) -plugin=protoc-gen-eams -I./$(PROTO_DIR) -eams_out=./$(PROTO_GEN_DIR). # This rulle is used to generate the message source files based $(info Done generating source files based on *.proto files.) # Convert the filenames of source files to object names.ĮMBEDDED_PROTO_OBJS := $(EMBEDDED_PROTO_SRC:%%.cpp=$(OBJECT_DIR)/%%.o) If you are working from the example repository you can check it out and pull the submodule in one command: The following chapter describes how you can do the same for your project. Here we are using Embedded Proto as a git submodule which still needs to be initiated. When building, all build results will be placed in the build folder.Īfter cloning the example repository, you will not yet have the embeddedproto folder. There are two in this case request.proto and reply.proto. The STM HAL is placed in the source folder to support the board.Īll *.proto files for this example are located in the proto folder. The example code on GitHub is based on a NUCLEO-F466RE board by ST Microelectronics. The src folder contains the source files for this example. In this example, we will use the following folder structure: VersionThis example is up to date with version 3.4.2 of the source code.

Cmake install files wildcard