[CMake] How to handle dependencies of protobuf files ?

Hi, I stumbled upon a problem with protobuf files, I attached a testcase. There is a MyBase.proto, which is "imported" by Complex.proto. If MyBase.proto is modified, protoc is run again in MyBase.proto, but not on Complex.proto, although it should. You can have a look at the attached example.

Re: [cmake-developers] target_link_libraries not callable from other directory scopes

On Thu, Apr 26, 2018 at 4:22 AM, Patrick Stotko < sto...@informatik.uni-bonn.de> wrote: > Hi, > > this nice post (https://crascit.com/2016/01/3 > 1/enhanced-source-file-handling-with-target_sources/) mentions some > modern usage of target_sources(), but also shows some discrepancy between >

[Cmake-commits] CMake branch, master, updated. v3.11.1-645-g48dcb2c

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180426) +set(CMake_VERSION_PATCH 20180427) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[Cmake-commits] CMake branch, master, updated. v3.11.1-626-g5858267

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5858267df6a1538ae0af8d503cd7f20b69c3f503 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.1-9-gb58e41c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via b58e41ccbd606106ee581943c8af92f8bfd5d535 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-633-g6fd60c6

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 6fd60c6ef0053406b4a88fc2b79c00f49c5bac7a (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.1-11-ga92ee4e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via a92ee4e30d57ef957a7a2ff4e0d5066136a2f6c2 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-623-gcaf6d93

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via caf6d93acd499aaa200f0b1338c334048f7f35f7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-619-g3f673f9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 3f673f9b27e46118add02bc41ec2c8aa78a1fe05 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-644-ge52cf10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e52cf1034f1cb712dca28131fc113db0fb580db9 (commit) via