Project fails to configure in cmake since i updated emsdk to 6.0.6

未关闭
#27,520 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
cmake, wasm
领域
build-system

调研方向

从 CMake 的 FindThreads.cmake 以及 third_party/or_tools/cmake/system_deps.cmake:17 和 third_party/or_tools/CMakeLists.txt:450 中的调用入手。在禁用 pthreads 的情况下,对比 emsdk 6.0.4 和 6.0.6 的配置,并检查 Abseil 是否出现相同的失败。受影响的项目能够在未启用线程的情况下成功完成配置,即为完成。

由索引模型根据 Issue 内容生成。

描述

Hello,

My project depends on or_tools third party project, which has those lines in cmake:

set(CMAKE_THREAD_PREFER_PTHREAD TRUE)
set(THREAD_PREFER_PTHREAD_FLAG TRUE)
find_package(Threads REQUIRED)

The thing is I do not need threads (threads aren't enabled in my root CMakeLists.txt).
So I absolutely have no idea how this was working before. It was just working about 2 years so I didn't ask questions...

But now it fails:

CMake Error at C:/Program Files/CMake/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
Could NOT find Threads (missing: Threads_FOUND)
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)
C:/Program Files/CMake/share/cmake-3.30/Modules/FindThreads.cmake:226 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
third_party/or_tools/cmake/system_deps.cmake:17 (find_package)
third_party/or_tools/CMakeLists.txt:450 (include)

Yesterday everything was fine. Since yesterday i just upgraded Python from 3.10.0 to 3.10.11 and emsdk to 6.0.6 (do not remember exactly which version was before, probably 6.0.4).

I doubt Python broke Threads setup in cmake.

Is anything were changed in emsdk regarding Threads setup with disabled pthreads recently ?

P.S. It's not just or_tools. Tried to disable Threads in or_tools:
if (NOT EMSCRIPTEN)
find_package(Threads REQUIRED)
endif()

But it fails in many other projects. For example Abseil also fails with the same error.

主要语言
C++
星标
27.8k
派生
3.6k
平均合并
1 天 3 小时
30 天内合并 PR
179

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

emscripten-core/emscripten 的其他 Issue

查看 emscripten-core/emscripten 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。