[Qt-creator] QtCreator 4.3 Beta and CMake 3.7.x Server Mode Slowness

[Mike Jackson]

Tobias Hunger wrote:
> On Wed, 2017-03-29 at 15:32 -0400, Mike Jackson wrote:
>>> I did look into the duplicate Source Directories you reported today.
>>> Those are caused by the same target being listed for different
>>> projects, but so far I could not see how those targets ended up in
>>> different projects. I think that is not even allowed in cmake, IIRC
>>> the target names need to be unique per build system. I will need to
>>> check the docs again to make sure though.
>>>
>>> I need to think about what to do in such a situation. It will probably
>>> be best to mark up the targets as "project::target" or something and
>>> keep them separate.
>> I would vote for that just to help us clean up our CMake codes. If we
>> have something messed up that the other generators deal better with
>> (Althrough the Xcode generator would show similar issues) then it would
>> be a big help for us.
>
> I asked on the cmake list and they pointed here:
>
> https://cmake.org/cmake/help/v3.8/policy/CMP0002.html
>
> So having the same target name below different project names in one bigger build
> system is a bug. Technically I would feel fine to just ignore the issue, but
> then I will keep getting bug reports about broken cmake projects going forward.
> There seem to be a lot of those out there:-).
>
> Best Regards,
> Tobias
>

I wonder if this issue has to do with the use of the following:

set_property(GLOBAL PROPERTY USE_FOLDERS ON)
  which we set in our projects so we can organize the projects in Visual 
Studio and Xcode. I set it to OFF but did not see any difference with 
the "multiple <source directory>" issue.

Would it be possible to hack the QtCreator source code to prepend to 
each "<Source Directory>" entry in the project tree with the project it 
was created under? I really want to figure out where the issue lies in 
our CMake codes.

Or is it just the fact that we have multiple "project()" invocations in 
our CMake hierarchy that is the problem.
-- 
Michael A. Jackson
BlueQuartz Software, LLC
[e]: mike.jackson at bluequartz.net