Re: [CMake] include_extenal_msproject() dependency behavior change between 3.13.4 and 3.14.0-rc2 (possible bug in rc2)

On Tue, Feb 26, 2019 at 10:06 PM wrote: > Hi Craig, > > Thanks for the info. I've verified that the revision you pointed me to > (24b6e4830d9027e63db7dfafa500aaeb652d3a4c) is where the behavior broke > (I built CMake using the revision directly before this one and > everything still works fine).

Re: [CMake] include_extenal_msproject() dependency behavior change between 3.13.4 and 3.14.0-rc2 (possible bug in rc2)

Hi Craig, Thanks for the info. I've verified that the revision you pointed me to (24b6e4830d9027e63db7dfafa500aaeb652d3a4c) is where the behavior broke (I built CMake using the revision directly before this one and everything still works fine). I'm no expert with CMake development - could

Re: [CMake] include_extenal_msproject() dependency behavior change between 3.13.4 and 3.14.0-rc2 (possible bug in rc2)

If you're able to build CMake from sources yourself, you may want to check if the changes from this merge request are what has led to the change you're seeing. That relates to how the EXCLUDE_FROM_ALL target property is initialised when

[CMake] include_extenal_msproject() dependency behavior change between 3.13.4 and 3.14.0-rc2 (possible bug in rc2)

Hello, We have a fairly large CMake project which uses include_extenal_msproject() when we are producing Visual Studio solutions to bring in projects produced using another build metadata generator. We've noticed most of our Visual Studio builds have started failing after switching to CMake