debugee
debugee
> Support for mac frameworks was added to CMake Tools a while ago. https://github.com/microsoft/vscode-cmake-tools/pull/3247. Though it does require a recent version of CMake. Setting a mac framework path in the...
@bobbrow @sean-mcmanus cmake-tools把framework当includes使用了 而且你说的这个https://github.com/microsoft/vscode-cmake-tools/pull/3247 并没有解决#include 这种方式,因为丢失了framework路径 我手动添加target_compile_options(qt-test PRIVATE -iframework/users/admin/qt/6.7.2/macos/lib) 就好了,但是cpptools有一个致命的问题, QMessageBox 文件无后缀,导致进一步goto的时候,cpptools把QMessageBox当源文件使用了也就是translate unit 已经改变了 而且分开处理includes和flags中的include设置,会导致严重的优先级紊乱 https://github.com/microsoft/vscode-cmake-tools/issues/4597 这不仅仅是cmake-tools的问题,设计上都有问题,分开处理包含路径就会丢失优先级
@bobbrow @sean-mcmanus https://github.com/debugee/bug-sample cmake_minimum_required(VERSION 3.30) set(CMAKE_VERBOSE_MAKEFILE ON) project(sample VERSION 0.1 LANGUAGES C CXX) add_executable(sample sample.cpp ) add_library(dynamicFramework SHARED dynamicFramework.cpp dynamicFramework.h ) set_target_properties(dynamicFramework PROPERTIES FRAMEWORK TRUE SYSTEM TRUE PUBLIC_HEADER dynamicFramework.h )...
> Hi @debugee . We're working on a fix for this. In the meanwhile, it should be possible to work around the issue by configuring CMake to generate a `compile_commands.json`...
sourceFileConfiguare function look like support system directory and framework，but if have compiler and compile options like -I ， cpptools do not known where it insert to this include list，include list...
I suggest that cmake fileapi does not separate the framework directory from includes into frameworks, so that includes contains all directories, including those included by -I, -F, -iframework, -isystem, etc.,...
@Colengms You can never fix this because cmake and cmake-tools have lost the precedence of directories, and the interface does not pass a flag indicating whether it is a system...
how to verify ? Are there any repair details?
> [@debugee](https://github.com/debugee) You can run C/C++: Log Diagnostics to see if the framework paths are correctly picked up as framework paths instead of normal include paths. After switching to the...
> [@debugee](https://github.com/debugee) You can run C/C++: Log Diagnostics to see if the framework paths are correctly picked up as framework paths instead of normal include paths. After switching to the...