(foundationpose) root@localhost:/mnt/e/wsl/foundationpose-main# -- The CXX compiler identification is GNU 13.3.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found Python3: /root/anaconda3/envs/foundationpose/bin/python3.9 (found suitable version "3.9.23", minimum required is "3.8") found components: Interpreter Development Development.Module Development.Embed -- Found OpenMP_CXX: -fopenmp (found version "4.5") -- Found OpenMP: TRUE (found version "4.5") -- Performing Test HAS_FLTO -- Performing Test HAS_FLTO - Success -- Found pybind11: /root/anaconda3/envs/foundationpose/include (found version "2.13.6") -- Configuring done (3.5s) CMake Error at /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/cmake/data/share/cmake-4.0/Modules/FindPython/Support.cmake:4331 (add_library): Cannot find source file: src/file_io.cpp Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .hip .ispc Call Stack (most recent call first): /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/cmake/data/share/cmake-4.0/Modules/FindPython3.cmake:643:EVAL:2 (__Python3_add_library) /root/anaconda3/envs/foundationpose/share/cmake/pybind11/pybind11NewTools.cmake:269 (python3_add_library) CMakeLists.txt:32 (pybind11_add_module) CMake Error at /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/cmake/data/share/cmake-4.0/Modules/FindPython/Support.cmake:4331 (add_library): No SOURCES given to target: mycpp Call Stack (most recent call first): /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/cmake/data/share/cmake-4.0/Modules/FindPython3.cmake:643:EVAL:2 (__Python3_add_library) /root/anaconda3/envs/foundationpose/share/cmake/pybind11/pybind11NewTools.cmake:269 (python3_add_library) CMakeLists.txt:32 (pybind11_add_module) CMake Generate step failed. Build files cannot be regenerated correctly. Obtaining file:///mnt/e/wsl/foundationpose-main/bundlesdf/mycuda Preparing metadata (setup.py) ... done Installing collected packages: common DEPRECATION: Legacy editable install of common==0.0.0 from file:///mnt/e/wsl/foundationpose-main/bundlesdf/mycuda (setup.py develop) is deprecated. pip 25.3 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457 Running setup.py develop for common error: subprocess-exited-with-error × python setup.py develop did not run successfully. │ exit code: 1 ╰─> [83 lines of output] /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'extra_cflags' warnings.warn(msg) /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'extra_cuda_cflags' warnings.warn(msg) running develop /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/cmd.py:90: DevelopDeprecationWarning: develop command is deprecated. !! **** Please avoid running ``setup.py`` and ``develop``. Instead, use standards-based tools like pip or uv. By 2025-Oct-31, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://github.com/pypa/setuptools/issues/917 for details. !! self.initialize_options() Obtaining file:///mnt/e/wsl/foundationpose-main/bundlesdf/mycuda Installing build dependencies: started Installing build dependencies: finished with status 'done' Checking if build backend supports build_editable: started Checking if build backend supports build_editable: finished with status 'done' Getting requirements to build editable: started Getting requirements to build editable: finished with status 'error' error: subprocess-exited-with-error × Getting requirements to build editable did not run successfully. │ exit code: 1 ╰─> [19 lines of output] Traceback (most recent call last): File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module> main() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main json_out["return_val"] = hook(hook_input["kwargs"]) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 157, in get_requires_for_build_editable return hook(config_settings) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 473, in get_requires_for_build_editable return self.get_requires_for_build_wheel(config_settings) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=[]) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 512, in run_setup super().run_setup(setup_script=setup_script) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 317, in run_setup exec(code, locals()) File "<string>", line 12, in <module> ModuleNotFoundError: No module named 'torch' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build editable did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Traceback (most recent call last): File "<string>", line 2, in <module> File "<pip-setuptools-caller>", line 35, in <module> File "/mnt/e/wsl/foundationpose-main/bundlesdf/mycuda/setup.py", line 21, in <module> setup( File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/init.py", line 115, in setup return distutils.core.setup(attrs) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 186, in setup return run_commands(dist) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 202, in run_commands dist.run_commands() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 1002, in run_commands self.run_command(cmd) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/dist.py", line 1102, in run_command super().run_command(command) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 1021, in run_command cmd_obj.run() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/command/develop.py", line 39, in run subprocess.check_call(cmd) File "/root/anaconda3/envs/foundationpose/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/root/anaconda3/envs/foundationpose/bin/python', '-m', 'pip', 'install', '-e', '.', '--use-pep517', '--no-deps']' returned non-zero exit status 1. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × python setup.py develop did not run successfully. │ exit code: 1 ╰─> [83 lines of output] /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'extra_cflags' warnings.warn(msg) /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'extra_cuda_cflags' warnings.warn(msg) running develop /root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/cmd.py:90: DevelopDeprecationWarning: develop command is deprecated. !! Please avoid running ``setup.py`` and ``develop``. Instead, use standards-based tools like pip or uv. By 2025-Oct-31, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://github.com/pypa/setuptools/issues/917 for details. !! self.initialize_options() Obtaining file:///mnt/e/wsl/foundationpose-main/bundlesdf/mycuda Installing build dependencies: started Installing build dependencies: finished with status 'done' Checking if build backend supports build_editable: started Checking if build backend supports build_editable: finished with status 'done' Getting requirements to build editable: started Getting requirements to build editable: finished with status 'error' error: subprocess-exited-with-error × Getting requirements to build editable did not run successfully. │ exit code: 1 ╰─> [19 lines of output] Traceback (most recent call last): File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module> main() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main json_out["return_val"] = hook(hook_input["kwargs"]) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 157, in get_requires_for_build_editable return hook(config_settings) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 473, in get_requires_for_build_editable return self.get_requires_for_build_wheel(config_settings) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=[]) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 512, in run_setup super().run_setup(setup_script=setup_script) File "/tmp/pip-build-env-ph1fchyv/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 317, in run_setup exec(code, locals()) File "<string>", line 12, in <module> ModuleNotFoundError: No module named 'torch' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build editable did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Traceback (most recent call last): File "<string>", line 2, in <module> File "<pip-setuptools-caller>", line 35, in <module> File "/mnt/e/wsl/foundationpose-main/bundlesdf/mycuda/setup.py", line 21, in <module> setup( File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/init.py", line 115, in setup return distutils.core.setup(attrs) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 186, in setup return run_commands(dist) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 202, in run_commands dist.run_commands() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 1002, in run_commands self.run_command(cmd) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/dist.py", line 1102, in run_command super().run_command(command) File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 1021, in run_command cmd_obj.run() File "/root/anaconda3/envs/foundationpose/lib/python3.9/site-packages/setuptools/command/develop.py", line 39, in run subprocess.check_call(cmd) File "/root/anaconda3/envs/foundationpose/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/root/anaconda3/envs/foundationpose/bin/python', '-m', 'pip', 'install', '-e', '.', '--use-pep517', '--no-deps']' returned non-zero exit status 1. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip.

时间: 2025-07-26 21:22:27 浏览: 18

<think>我们正在处理两个主要问题： 1. CMake构建时找不到src/file_io.cpp文件 2. 使用setup.py develop安装时因缺少torch模块而失败首先，我们需要分析问题原因，然后提供解决方案。问题1: CMake找不到src/file_io.cpp文件可能的原因： - 文件路径错误：CMakeLists.txt中指定的路径与项目实际结构不符 - 文件不存在：该文件确实不在指定位置 - 大小写敏感：在Linux系统中，路径大小写敏感问题2: setup.py develop因缺少torch模块而失败可能的原因： - 未安装torch或安装不正确 - 环境问题：可能使用了错误的环境，或者环境未激活 - 在setup.py中未正确声明依赖根据引用[2]中的信息，有些组件需要手动编译，例如使用`python setup.py install`。同时，引用[3]中出现了CMake错误，涉及到CUDA和torch的配置，这暗示了torch可能没有正确安装或者环境变量设置有问题。解决方案：一、解决CMake找不到src/file_io.cpp文件步骤1：检查文件是否存在 - 确认项目根目录下是否存在`src/file_io.cpp`文件。如果不存在，需要检查项目结构，或者从源代码仓库中确认该文件是否被移动或删除。步骤2：调整CMakeLists.txt中的文件收集方式 - 使用`file(GLOB ...)`命令收集源文件时，如果文件路径不匹配，会导致文件未被包含。建议检查当前CMakeLists.txt中的文件收集部分，并确保路径正确。例如，原配置可能是： ```cmake file(GLOB MY_SRC ${PROJECT_SOURCE_DIR}/src/*.cpp) ``` 如果`file_io.cpp`位于`src/app`子目录下，则需要调整GLOB模式以包含子目录： ```cmake file(GLOB_RECURSE MY_SRC ${PROJECT_SOURCE_DIR}/src/*.cpp) ``` 注意：使用`GLOB_RECURSE`会递归搜索src目录下的所有子目录。但要注意，如果项目结构复杂，可能会包含不需要的文件。或者，如果知道文件的确切路径，可以显式添加： ```cmake set(MY_SRC src/app/file_io.cpp ... # 其他文件 ) ``` 步骤3：确保路径大小写正确 - 检查CMakeLists.txt中路径的大小写是否与实际文件系统一致。二、解决setup.py develop因缺少torch模块而失败步骤1：确认torch安装 - 在终端中激活项目使用的Python环境，然后运行： ```bash python -c "import torch; print(torch.__version__)" ``` 如果导入失败，说明torch未安装或安装不正确。步骤2：安装torch - 根据项目要求，安装正确版本的torch。通常项目文档会指定版本，如果没有，可以尝试： ```bash pip install torch torchvision ``` 或者使用项目指定的版本，例如： ```bash pip install torch==1.7.1+cu110 torchvision==0.8.2+cu110 -f https://download.pytorch.org/whl/torch_stable.html ``` 步骤3：检查环境 - 确保在运行setup.py时，使用的是同一个环境下的Python。步骤4：在setup.py中声明依赖 - 如果项目使用setuptools，则应在setup.py中声明依赖。检查setup.py是否包含`install_requires`字段，并包含'torch'。例如： ```python setup( ... install_requires=['torch', 'torchvision'], ... ) ``` 然后重新运行`python setup.py develop`，它会自动安装缺失的依赖。步骤5：手动安装依赖 - 如果setup.py没有声明依赖，可以手动安装项目所需依赖。通常项目会提供requirements.txt，使用： ```bash pip install -r requirements.txt ``` 步骤6：处理引用[2]中提到的pybind11问题 - 引用[2]提到在编译fast_gicp时使用了`python setup.py install`，并遇到了pybind11错误。如果我们的项目也使用pybind11，需要确保pybind11已安装。可以通过pip安装： ```bash pip install pybind11 ``` 三、综合建议由于项目可能包含多个组件，有些通过CMake构建，有些通过setuptools构建，因此需要分别处理。建议的完整步骤： 1. 创建并激活合适的Python环境（如conda或venv） 2. 安装项目所需的主要依赖，如torch、torchvision、pybind11等 3. 对于CMake部分： - 调整CMakeLists.txt中的源文件路径，确保包含所有需要的文件 - 创建build目录，运行cmake配置和构建 4. 对于Python部分： - 如果项目包含setup.py，确保其中声明了依赖，然后运行`python setup.py develop`或`pip install -e .` 注意：引用[3]中的CMake错误可能与CUDA配置有关，如果遇到类似错误，需要检查CUDA路径和版本是否与torch版本匹配。如果问题仍然存在，请提供具体的错误信息，以便进一步诊断。示例CMakeLists.txt修改（针对文件路径问题）：原始配置： ```cmake file(GLOB MY_SRC ${PROJECT_SOURCE_DIR}/src/*.cpp) ``` 修改为（递归查找）： ```cmake file(GLOB_RECURSE MY_SRC ${PROJECT_SOURCE_DIR}/src/*.cpp ${PROJECT_SOURCE_DIR}/src/*.cu # 如果有CUDA文件 ) ``` 或者显式列出文件（推荐，避免包含不需要的文件）： ```cmake set(MY_SRC src/file_io.cpp src/app/main.cpp # ... 其他文件 ) ``` 示例setup.py修改（添加依赖）： ```python from setuptools import setup, Extension setup( name='my_project', version='0.1', ext_modules=[...], install_requires=[ 'torch', 'pybind11', # 其他依赖 ], ) ``` 最后，根据引用[5]，训练模型时可能需要进入特定目录运行脚本，确保在正确环境中运行。如果用户的问题涉及特定项目（如CenterNet），请参考项目文档的安装说明。由于用户提到的是降级到CMake 3.15，因此上述解决方案均需在CMake 3.15环境下验证。如果用户提供的引用中有其他线索，请结合使用。注意：在修改构建脚本后，清理构建目录（删除build目录）再重新构建。生成相关问题： 1. 如何正确设置CMakeLists.txt以递归包含源文件？ 2. 在setup.py中如何正确声明torch依赖？ 3. 如何解决CMake构建中关于CUDA配置的错误？ 4. 使用setup.py develop安装项目时如何避免依赖缺失？ 5. 如何检查Python环境中是否已安装torch？</think>### 解决CMake文件缺失与Python模块安装问题 #### 问题1：CMake找不到`src/file_io.cpp`文件 **原因分析**： 1. 文件路径错误：CMakeLists.txt中的路径配置与实际文件位置不匹配 2. 文件未包含在构建系统中：未正确添加到`file(GLOB)`或`add_library`指令 3. 大小写敏感问题：Linux系统下路径大小写敏感 **解决方案**： ```cmake # 修改CMakeLists.txt # 1. 检查文件路径 message(STATUS "当前路径: ${PROJECT_SOURCE_DIR}") # 验证根目录 # 2. 使用精确路径指定源文件 file(GLOB MY_SRC ${PROJECT_SOURCE_DIR}/src/*.cpp ${PROJECT_SOURCE_DIR}/src/app/*.cpp # 添加子目录 ) # 3. 显式包含关键文件 list(APPEND MY_SRC ${PROJECT_SOURCE_DIR}/src/file_io.cpp # 显式添加 ) # 4. 验证文件存在 foreach(file ${MY_SRC}) if(NOT EXISTS ${file}) message(WARNING "缺失文件: ${file}") endif() endforeach() ``` #### 问题2：`setup.py develop`安装失败（缺少torch模块） **原因分析**： 1. 环境未正确激活：未在虚拟环境中操作 2. PyTorch未正确安装：版本不匹配或安装不完整 3. 路径配置错误：Python解释器路径与CMake不匹配 **解决方案**： ```bash # 步骤1：创建并激活虚拟环境 python -m venv .venv source .venv/bin/activate # Linux/Mac # .venv\Scripts\activate # Windows # 步骤2：安装匹配的PyTorch版本 # 根据项目要求选择版本（示例） pip install torch==1.10.0+cu113 torchvision==0.11.1+cu113 -f https://download.pytorch.org/whl/torch_stable.html # 步骤3：验证安装 python -c "import torch; print(torch.__version__)" # 步骤4：配置CMake的Python路径 cmake -B build \ -DPYTHON_EXECUTABLE="$(which python)" \ -Dpybind11_DIR="$(pip show pybind11 | grep Location | cut -d' ' -f2)/pybind11/share/cmake/pybind11" ``` #### 完整构建流程 ```bash # 1. 准备环境 python -m venv .venv source .venv/bin/activate pip install -r requirements.txt # 包含torch/pybind11等 # 2. 配置CMake cmake -B build \ -DCMAKE_BUILD_TYPE=Release \ -DPYTHON_EXECUTABLE="$(which python)" # 3. 构建C++扩展 cmake --build build --parallel 4 # 4. 安装Python模块 cd python python setup.py develop # 现在应能正确识别torch ``` #### 关键问题排查点 1. **路径验证**： ```bash # 检查CMake识别的Python路径 cmake -B build -L | grep PYTHON ``` 2. **Torch安装验证**： ```python # test_torch.py import torch print(f"CUDA可用: {torch.cuda.is_available()}") print(f"CUDA版本: {torch.version.cuda}") ``` 3. **文件结构检查**： ```bash # 确认文件位置 find . -name file_io.cpp # 输出应为: ./src/app/file_io.cpp ``` > **重要提示**：对于包含C++扩展的Python包，必须确保： > 1. CMake使用的Python解释器与`setup.py`运行时相同 > 2. PyTorch版本与CUDA驱动兼容（使用`nvcc --version`验证） > 3. 在虚拟环境中完成所有操作[^4]

阅读全文

CSDN会员

开通CSDN年卡参与万元壕礼抽奖

海量 VIP免费资源千本正版电子书商城会员专享价千门课程&专栏

全年可省5,000元立即开通

大家在看

基于ADS的微带滤波器设计

Pixhawk4飞控驱动.zip

ztecfg中兴配置加解密工具3.0版本.rar

配置车辆-feedback systems_an introduction for scientists and engineers

xilinx.com_user_IIC_AXI_1.0.zip

最新推荐

开发界面语义化：声控 + 画图协同生成代码.doc

Python程序TXLWizard生成TXL文件及转换工具介绍

【创新图生成：扣子平台的技术前沿与创新思维】：引领图像生成技术的新潮流

海康威视机器视觉工程师考核

Linux环境下Docker Hub公共容器映像检测工具集

【扣子平台图像艺术探究：理论与实践的完美结合】：深入学习图像生成的艺术

增广路定理的证明

Pulse：基于SwiftUI的Apple平台高效日志记录与网络监控

【深入扣子平台：图像生成机制全揭秘】：掌握背后技术，提升图像生成效率

对RTL跑regression是什么意思