Observed this situation many times as well - good to know the answer: is there 
a way to handle, bug or missed feature?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



27.08.2018, 08:23, "Abir Basak" <abirba...@gmail.com>:
> Hi,
>   When I open a CMake INTERFACE project, do not see the header files in the 
> QtC Projects pane. This is not problem with executable or library project.
>   Presently as a workaround I made a custom target adding the header files, 
> e.g.
>  add_custom_target(dummy SOURCES ${HEADERS})
> This solves the problem partially listing the header files under a separate 
> target node 'dummy' , but misses language features.
>  So it shows all sorts of wrong analysis like include file not found, or 
> requires c++17 extension etc. Those settings are all present for the actual 
> target like target_compile_features, target_Include_directories , but can't 
> be placed on custom target which is not a compilable target.
>
>  Is there a proper way to handle INTERFACE projects so that QtC understands 
> it and doesn't show wrong analysis (btw, the project itself is fine, runs all 
> tests & examples correctly, only the analysis in QtC is misleading & doesn't 
> show the headers without custom target, even with target_sources)
>
> Thanks
> ,
>
> _______________________________________________
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to