QT Creator和OpenCV455：＆＃x27; arm_neon.h＆＃x27;找不到文件
我正在使用QT6和OPENCV455构建一个项目。我正在用硅芯片（ARM64）在新的MacBook上进行此操作。我可以不用错误编译整个项目，但是我总是会在编辑器中找到'arm_neon.h'文件错误消息，因此语法突出显示和警告显示无法正常工作。代码。我在下面添加了更多详细信息 - 任何帮助。
堆栈：
QT创建者7.0.1 基于QT 6.2.3（Clang 13.0（Apple），64位） 根据官方文档
错误：
xh：在随附的文件中：'arm_neon.h'文件中未找到 自我编译的OPENCV 455版本。 CV_CPU_DISPATCH.H：219：12：
我尝试过的错误发生了错误：
重新安装所有内容，重新编译OpENCV，重新安装命令行工具，更新命令行工具，仔细检查每个链接。
I'm building a project using qt6 and opencv455. I'm doing this on the new MacBook with a silicon chip (arm64). I can compile the whole project without errors, but I always get the 'arm_neon.h' file not found error message in the editor and therefore the syntax highlighting and warning display doesn't work correctly for the rest of the code. I've added some more details below - any help appreciated.
Stack:
Qt Creator 7.0.1
Based on Qt 6.2.3 (Clang 13.0 (Apple), 64 bit)
Self compiled OpenCv 455 version according to official docs
Error:
X.h: In included file: 'arm_neon.h' file not found
cv_cpu_dispatch.h:219:12: error occurred here
What I've tried:
Re-installing everything, recompiling opencv, reinstalling the command line tools, updating the command line tools, double checked every link.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
好的，在三天重新安装并重新编译所有可能的配置（例如带有Unix Makefiles，Xcode，Xcode，强制的ARM64等目标架构）中的所有内容之后，我找到了一个解决方案。最终有效的是禁用
clangcodeModelflag在qtcreator的插件（菜单：about/plugins/ - ＆gt;搜索clangcodemodel> clangcodemodel ），禁用插件并重新启动应用程序。 。非常感谢。
Okay, I found a solution after three days of re-installing and re-compiling everything in every possible configuration (like opencv with unix makefiles, xcode, forced target architecture of arm64 etc). What finally worked was to disable the
ClangCodeModelflag in the plugin section of QtCreator (Menu: About/Plugins/ -> search forClangCodeModel, disable the plugin and restart the application.I'm pretty sure this is just a workaround, but at least I can work now as it should be and maybe this helps someone else. If anyone has some input on how to fix this issue at its core, any help or alternative answer is very appreciated.