I set the policy on our project to both new and old and I don't see any
difference in how QtCreator is loading the project from CMake. I guess
if I could debug the cmake that is coming back from CMake I might be
better able to understand what we are doing in the DREAM.3D CMake that
is causing the issue.
--
Michael A. Jackson 400 S. Pioneer Blvd
Owner, President Springboro, Ohio 45066
BlueQuartz Software, LLC EMail: mike.jack...@bluequartz.net
Voice: 937-790-1601 Web: http://www.bluequartz.net
Fax: 937-746-0783
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
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
