cmake:CMAKE_SYSTEM_PROCESSOR为空是怎么回事儿?

原创 已于 2023-12-29 14:04:06 修改 · 7.2k 阅读 · 8 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#cmake #CMAKE_SYSTEM_PROCESSOR #empty

于 2018-10-17 11:15:29 首次发布
本文详细解析了在使用CMake进行交叉编译时,CMAKE_SYSTEM_NAME和CMAKE_SYSTEM_PROCESSOR参数的重要性。若仅设置CMAKE_SYSTEM_NAME而忽略CMAKE_SYSTEM_PROCESSOR,会导致后者值为空的错误。文章通过实例演示正确配置方法。

今天执行cmake创建Makefile的时候出了个怪事：CMAKE_SYSTEM_PROCESSOR的值为空
反复测试到到了原因：我在执行cmake时加了参数-DCMAKE_SYSTEM_NAME=Linux

cmake  . -G "Eclipse CDT4 - Unix Makefiles"  -DCMAKE_SYSTEM_NAME=Linux

根据cmake官方关于交叉编译的介绍: 《Cross Compiling for Linux》,CMAKE_SYSTEM_NAME和CMAKE_SYSTEM_PROCESSOR是交叉编译的时候必须指定的两个参数。

所以如果在cmake命令行定义了CMAKE_SYSTEM_NAME,就必须也定义CMAKE_SYSTEM_PROCESSOR，如下。

cmake  . -G "Eclipse CDT4 - Unix Makefiles"  \
	-DCMAKE_SYSTEM_NAME=Linux \
	-DCMAKE_SYSTEM_PROCESSOR=x86_64

如果在命令行只是定义了CMAKE_SYSTEM_NAME,就会出现CMAKE_SYSTEM_PROCESSOR为空这种奇怪的问题。

另外经测试如果在CMakeLists.txt脚本中用set命令设置CMAKE_SYSTEM_NAME的值,并不会影响CMAKE_SYSTEM_PROCESSOR的值：

set(CMAKE_SYSTEM_NAME Linux)
CMake入门教程【基础篇】跨平台判断宏
小鱼酱的博客
01-02 1518
CMake跨平台判断
CMAKE交叉编译
xiyuan的博客
07-27 531
代表了一系列的相关文件夹路径的根路径的变更，比如你设置了/opt/arm/,所有的Find_xxx.cmake都会优先根据这个路径下的/usr/lib,/lib等进行查找，然后才会去你自己的/usr/lib和/lib进行查找，如果你有一些库是不被包含在/opt/arm里面的，你也可以显示指定多个值给CMAKE_FIND_ROOT_PATH。对FIND_LIBRARY()起作用，表示在链接的时候的库的相关选项，因此这里需要设置成ONLY来保证我们的库是在交叉环境中找的.同上，此时代表的是C++编译器。
【CMake 入门与进阶（13）】 CMake如何设置交叉编译（附代码）
热门推荐
cj_lsk的博客
06-23 1万+
通过-DCMAKE_TOOLCHAIN_FILE 选项指定配置文件，-D 是 cmake 命令提供的一个选项，通过该选项可以创建一个缓存变量（缓存变量就是全局变量，在整个工程中都是生效的，会覆盖 CMakeLists.txt 源码中定义的同名变量 ），所以 -DCMAKE_TOOLCHAIN_FILE 其实就是设置了缓存变量 CMAKE_TOOLCHAIN_FILE，它的值就是“=”号后面的内容，cmake 会执行 CMAKE_TOOLCHAIN_FILE 变量所指定的源文件，对交叉编译进行设置；
Cmake使用教程
Yu_Lijing的博客
07-16 2550
本篇博客介绍了cmake项目构建工具的安装和使用，以供大家很本人日常开发时进行参考。cmake在大型项目中非常吃香，一定要灵活应用。
cmake 报错 from cmake import cmake
weixin_46106405的博客
03-14 2686
使用cmake编译CMakeLists.txt报错: Traceback (most recent call last): File "/home/roots/.local/bin/cmake", line 7, in <module> from cmake import cmake ModuleNotFoundError: No module named 'cmake' 问题的原因: 系统自带的python3中没有安装cmake 解决方案: pip3 install cmake
cmake 检测处理器指令集
luoganttcc_son的博客
07-29 436
代码】cmake检测处理器指令集。
CMake编译时FFMPEG一直显示Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.26100. CMake Warning (dev) at D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC.cmake:556 (enable_language): project() should be called prior to this enable_language() call. Call Stack (most recent call first): D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC.cmake:529 (__windows_compiler_msvc_enable_rc) D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC-CXX.cmake:6 (__windows_compiler_msvc) D:/CMake/share/cmake-4.0/Modules/CMakeCXXInformation.cmake:48 (include) CMakeLists.txt:107 (enable_language) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC.cmake:556 (enable_language): project() should be called prior to this enable_language() call. Call Stack (most recent call first): D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC.cmake:529 (__windows_compiler_msvc_enable_rc) D:/CMake/share/cmake-4.0/Modules/Platform/Windows-MSVC-C.cmake:5 (__windows_compiler_msvc) D:/CMake/share/cmake-4.0/Modules/CMakeCInformation.cmake:48 (include) CMakeLists.txt:107 (enable_language) This warning is for project developers. Use -Wno-dev to suppress it. Detected processor: AMD64 CMake Warning at cmake/OpenCVDetectCXXCompiler.cmake:177 (message): OpenCV does not recognize MSVC_VERSION "1943". Cannot set OpenCV_RUNTIME Call Stack (most recent call first): CMakeLists.txt:161 (include) CMake Warning at cmake/OpenCVUtils.cmake:758 (message): Unexpected option: WITH_CUFFT (=ON) Condition: IF (WITH_CUDA) Call Stack (most recent call first): CMakeLists.txt:251 (OCV_OPTION) CMake Warning at cmake/OpenCVUtils.cmake:758 (message): Unexpected option: WITH_CUBLAS (=ON) Condition: IF (WITH_CUDA) Call Stack (most recent call first): CMakeLists.txt:254 (OCV_OPTION) CMake Warning at cmake/OpenCVUtils.cmake:758 (message): Unexpected option: WITH_CUDNN (=ON) Condition: IF (WITH_CUDA) Call Stack (most recent call first): CMakeLists.txt:257 (OCV_OPTION)0K
05-12
cmake -DCMAKE_SYSTEM_VERSION=10.0.22621.0 .. ``` 3. 在系统环境变量中显式设置`WindowsSDKVersion=10.0.22621.0\`[^1] ### 二、project()调用顺序警告 该警告通常由CMakeLists.txt结构错误引起： ```cmake # ...
cmake -DSHERPA_ONNX_ENABLE_GPU=ON ..但执行这个操作的时候会从github下载，也会卡住 -- CMAKE_SYSTEM_NAME: Linux -- CMAKE_SYSTEM_PROCESSOR: x86_64 -- location_onnxruntime_header_dir: location_onnxruntime_header_dir-NOTFOUND -- location_onnxruntime_lib: location_onnxruntime_lib-NOTFOUND -- location_onnxruntime_cuda_lib: location_onnxruntime_cuda_lib-NOTFOUND -- Could not find a pre-installed onnxruntime. -- Downloading pre-compiled onnxruntime -- CMAKE_SYSTEM_NAME: Linux -- CMAKE_SYSTEM_PROCESSOR: x86_64 -- CMAKE_SYSTEM_NAME: Linux -- CMAKE_SYSTEM_PROCESSOR: x86_64 -- Downloading onnxruntime from https://github.com/csukuangfj/onnxruntime-libs/releases/download/v1.17.1/onnxruntime-linux-x64-gpu-1.17.1-patched.zip
08-27
我们面临的问题是在使用CMake构建sherpa-onnx项目时，由于网络原因无法从GitHub下载onnxruntime库（具体文件：onnxruntime-linux-x64-gpu-1.17.1-patched.zip）。由于CMake在构建过程中会自动下载依赖，网络不稳定会...
我都告诉你再E:\Libs里面 为什么你还要重新安装 OpenBLAS？你到底再干什么啊？我虚拟环境都不见了！！！！！”PS C:\Users\Administrator\Desktop> cd E:\PyTorch_Build\pytorch PS E:\PyTorch_Build\pytorch> python -m venv rtx5070_env No pyvenv.cfg file PS E:\PyTorch_Build\pytorch> .\rtx5070_env\Scripts\activate ParserError: E:\PyTorch_Build\pytorch\rtx5070_env\Scripts\activate.ps1:9 Line | 9 | if () { | ~ | Missing condition in if statement after 'if ('. PS E:\PyTorch_Build\pytorch> # 修复激活脚本 PS E:\PyTorch_Build\pytorch> $activateContent = @" >> # E:\PyTorch_Build\pytorch\rtx5070_env\Scripts\activate.ps1 >> param() >> >> # 设置环境变量 >> $env:VIRTUAL_ENV = "E:\PyTorch_Build\pytorch\rtx5070_env" >> $env:PATH = "E:\PyTorch_Build\pytorch\rtx5070_env\Scripts;" + $env:PATH >> >> # 移除旧的环境变量（如果存在） >> if ($env:_OLD_VIRTUAL_PATH) { >> $env:PATH = $env:_OLD_VIRTUAL_PATH >> } >> >> # 保存当前 PATH >> $env:_OLD_VIRTUAL_PATH = $env:PATH >> >> Write-Host "✅ 虚拟环境已激活: $env:VIRTUAL_ENV" -ForegroundColor Green >> "@ PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> $activateContent | Out-File "E:\PyTorch_Build\pytorch\rtx5070_env\Scripts\activate.ps1" -Encoding UTF8 -Force PS E:\PyTorch_Build\pytorch> # 修改 CMake 配置以支持 AMD64 PS E:\PyTorch_Build\pytorch> $qnnpackPath = "E:\PyTorch_Build\pytorch\aten\src\ATen\native\quantized\cpu\qnnpack\CMakeLists.txt" PS E:\PyTorch_Build\pytorch> (Get-Content $qnnpackPath) -replace >> "if\(CMAKE_SYSTEM_PROCESSOR MATCHES \"\^(i\[3-6]86\|x86_64\|amd64\)\$\"\)", >> 'if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(i[3-6]86|x86_64|amd64|AMD64)$")' | >> Set-Content $qnnpackPath ParserError: Line | 2 | "if\(CMAKE_SYSTEM_PROCESSOR MATCHES \"\^(i\[3-6]86\|x86_64\|amd64 … | ~~ | Unexpected token '\^' in expression or statement. PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> Write-Host "✅ 已修复 AMD64 处理器识别问题" ✅ 已修复 AMD64 处理器识别问题 PS E:\PyTorch_Build\pytorch> # 添加 CUDA 环境变量 PS E:\PyTorch_Build\pytorch> $env:CUDA_PATH = "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v13.0" PS E:\PyTorch_Build\pytorch> $env:PATH = "$env:CUDA_PATH\bin;$env:PATH" PS E:\PyTorch_Build\pytorch> $env:LIB = "$env:CUDA_PATH\lib\x64;$env:LIB" PS E:\PyTorch_Build\pytorch> $env:INCLUDE = "$env:CUDA_PATH\include;$env:INCLUDE" PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> # 验证 CUDA 安装 PS E:\PyTorch_Build\pytorch> Write-Host "🔍 验证 CUDA 安装:" 🔍 验证 CUDA 安装: PS E:\PyTorch_Build\pytorch> nvcc --version nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2025 NVIDIA Corporation Built on Wed_Jul_16_20:06:48_Pacific_Daylight_Time_2025 Cuda compilation tools, release 13.0, V13.0.48 Build cuda_13.0.r13.0/compiler.36260728_0 PS E:\PyTorch_Build\pytorch> # 安装 OpenBLAS 作为替代 PS E:\PyTorch_Build\pytorch> $openBlasUrl = "https://github.com/xianyi/OpenBLAS/releases/download/v0.3.27/OpenBLAS-0.3.27-x64.zip" PS E:\PyTorch_Build\pytorch> $openBlasPath = "E:\PyTorch_Build\OpenBLAS" PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> # 下载并解压 OpenBLAS PS E:\PyTorch_Build\pytorch> Invoke-WebRequest -Uri $openBlasUrl -OutFile "$openBlasPath.zip" PS E:\PyTorch_Build\pytorch> Expand-Archive -Path "$openBlasPath.zip" -DestinationPath $openBlasPath GAC Version Location --- ------- -------- False v4.0.30319 C:\Program Files\PowerShell\7\WindowsBase.dll OperationStopped: PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> # 设置 CMake 选项 PS E:\PyTorch_Build\pytorch> $cmakeOptions = @( >> "-S ." >> "-B build" >> "-GNinja" >> "-DCMAKE_BUILD_TYPE=Release" >> "-DUSE_CUDA=ON" >> "-DUSE_CUDNN=ON" >> "-DCUDA_TOOLKIT_ROOT_DIR=`"C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v13.0`"" >> "-DCUDNN_ROOT=`"E:/Program Files/NVIDIA/CUDNN/v9.12`"" >> "-DTORCH_CUDA_ARCH_LIST=`"8.6`"" >> "-DBUILD_PYTHON=ON" >> "-DBLAS=OpenBLAS" >> "-DOPENBLAS_HOME=`"$openBlasPath`"" >> "-DATEN_NO_TEST=ON" >> ) PS E:\PyTorch_Build\pytorch> PS E:\PyTorch_Build\pytorch> # 执行 CMake 配置 PS E:\PyTorch_Build\pytorch> cmake @cmakeOptions CMake Deprecation Warning at CMakeLists.txt:9 (cmake_policy): The OLD behavior for policy CMP0126 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. CMake Warning at CMakeLists.txt:421 (message): TensorPipe cannot be used on Windows. Set it to OFF CMake Warning at CMakeLists.txt:423 (message): KleidiAI cannot be used on Windows. Set it to OFF CMake Warning at CMakeLists.txt:435 (message): Libuv is not installed in current conda env. Set USE_DISTRIBUTED to OFF. Please run command 'conda install -c conda-forge libuv=1.39' to install libuv. -- Current compiler supports avx2 extension. Will build perfkernels. -- Could not find hardware support for NEON on this machine. -- No OMAP3 processor on this machine. -- No OMAP4 processor on this machine. -- Compiler does not support SVE extension. Will not build perfkernels. CMake Warning at CMakeLists.txt:841 (message): x64 operating system is required for FBGEMM. Not compiling with FBGEMM. Turn this warning off by USE_FBGEMM=OFF. -- Could NOT find CUDA (missing: CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY) (found version "13.0") CMake Warning at cmake/public/cuda.cmake:31 (message): PyTorch: CUDA cannot be found. Depending on whether you are building PyTorch or a PyTorch dependent library, the next warning / error will give you more info. Call Stack (most recent call first): cmake/Dependencies.cmake:44 (include) CMakeLists.txt:869 (include) CMake Warning at cmake/Dependencies.cmake:76 (message): Not compiling with CUDA. Suppress this warning with -DUSE_CUDA=OFF. Call Stack (most recent call first): CMakeLists.txt:869 (include) -- Building using own protobuf under third_party per request. -- Use custom protobuf build. CMake Warning at cmake/ProtoBuf.cmake:37 (message): Ancient protobuf forces CMake compatibility Call Stack (most recent call first): cmake/ProtoBuf.cmake:87 (custom_protobuf_find) cmake/Dependencies.cmake:107 (include) CMakeLists.txt:869 (include) CMake Deprecation Warning at third_party/protobuf/cmake/CMakeLists.txt:2 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. -- -- 3.13.0.0 -- Caffe2 protobuf include directory: $<BUILD_INTERFACE:E:/PyTorch_Build/pytorch/third_party/protobuf/src>$<INSTALL_INTERFACE:include> -- Trying to find preferred BLAS backend of choice: OpenBLAS -- Could not find OpenBLAS include. Turning OpenBLAS_FOUND off -- Could not find OpenBLAS lib. Turning OpenBLAS_FOUND off CMake Error at cmake/Modules/FindOpenBLAS.cmake:58 (MESSAGE): Could not find OpenBLAS Call Stack (most recent call first): cmake/Dependencies.cmake:182 (find_package) CMakeLists.txt:869 (include) -- Configuring incomplete, errors occurred! PS E:\PyTorch_Build\pytorch>“
最新发布
09-05
'if\(CMAKE_SYSTEM_PROCESSOR MATCHES "\^(i\[3-6]86\|x86_64\|amd64\)\$$"\)', 'if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(i[3-6]86|x86_64|amd64|AMD64)$")' | Set-Content $qnnpackPath # 5. 配置 CUDA 环境 $...
string(TOLOWER ${CMAKE_SYSTEM_PROCESSOR} CMAKE_SYSTEM_PROCESSOR_LC)解释
04-05
该命令将系统处理器名称转换为小写并将其存储在变量 CMAKE_SYSTEM_PROCESSOR_LC 中。例如，如果 CMAKE_SYSTEM_PROCESSOR 是 "x86_64"，则 CMAKE_SYSTEM_PROCESSOR_LC 将是 "x86_64" 的小写形式，即 "x86_64"。
cmake cmake_processor_name未定义
06-25
这将为项目中的所有 CMake 脚本提供一个名为 `cmake_processor_name` 的变量，并将其值设置为 `x86_64`。 #### 方法二：在 `CMakeLists.txt` 中定义变量 如果希望在 `CMakeLists.txt` 文件中直接定义该变量，可以...
CMake I 检测处理器体系结构
该用户还没想到好的昵称的博客
01-17 8912
检测处理器体系结构：x86、x64、AMD64。 检测处理器指令集：虚拟内存大小、CPU线程数、主机名...... CMAKE_SIZEOF_VOID_P、CMAKE_HOST_SYSTEM_PROCESSOR、CMAKE_SYS、cmake_host_system_information、configure_file、target_sources、target_include_directories PROJECT_SOURCE_DIR 、PROJECT_BINARY_DIR
在aarch64-himix100-linux-gcc下cmake报错（The C compiler identification is unknown）
qq_30841655的博客
09-10 2855
项目场景： 华为好望角AI摄像头C系列的算法移植过程中，遇到cmake报错 问题描述： gcc:aarch64-himix100-linux-gcc CMakeLists.txt文档： cmake_minimum_required(VERSION 3.14) project(NNIE_tutorial) set(CMAKE_CXX_STANDARD 14) set(CMAKE_CXX_COMPILER /home/liuky/HDD_1/soft/aarch-linux-gnu/bin/.
cmake学习笔记
小麒麟的成长之路
09-15 980
一、cmake常用变量和常用环境变量 1、cmake变量引用形式： cmake使用${}进行变量的引用，在if语句中直接使用变量名而不需要通过${}取值。 2、cmake自定义变量的方式： 分为显式定义和隐式定义，例如PROJECT指令，会隐式定义_BINARY_DIR和_SOURCE_DIR两个变量 显式定义使用SET指令，例如： SET(HELLO_SRC main.c)，则
【Cmake】执行cmake命令时报错：No XSLT processor found
郭老二
11-18 546
一、问题描述 在ubuntu中，在生成Doc(文档)中，执行cmake命令时报错：No XSLT processor found 二、原因查找 google该错误信息，原因是确实ubuntu中没有安装 xsltproc 三、解决方法 安装 xsltproc sudo apt install xsltproc 四、扩展 xsltproc是由DanielVeillard用来C语言编写的是一个快速X...
cmake命令大全
权哥的博客
09-26 2886
cmake命令大全 cmake中的预定义变量 project_source_dir 工程的根目录 project_binary_dir 运行cmake命令的目录，通常是 ${PROJECT_SOURCE_DIR}/build cmake_include_path 环境变量，非cmake变量 cmake_liibrary_path 环境变量 cmake_current_binar
cmake使用方法
u.意思的博客
07-11 762
cmake生成Makefile
CMake 入门与进阶
zhuguanlin121的博客
03-06 6698
目录cmake 简介cmake 和Makefilecmake 的下载cmake 的使用方法 在前面两篇内容中，我们编写了很多示例程序，但这些示例程序都只有一个.c 源文件，非常简单。所以，编译这些示例代码其实都非常简单，直接使用GCC 编译器编译即可，连Makefile 都不需要。但是，在实际的项目中，并非如此简单，一个工程中可能包含几十、成百甚至上千个源文件，这些源文件按照其类型、功能、模块分别放置在不同的目录中；面对这样的一个工程，通常会使用make 工具进行管理、编译，make 工具依赖于Makefi
[cmake]cmake编译工具链
FL1768317420的博客
03-27 1846
默认情况下，Cmake会根据所使用的编程语言，决定使用何种工具链来编译、链接、创建可执行文件。但是在交叉编译场景，那么最好通过工具链文件来指定编译、链接等信息。本文介绍Cmake工具链文件的相关内容。交叉编译：主机系统（host）和目标系统（target）不一样，也就是Cmake运行的环境（主机系统）和最终构建出来的可执行文件要运行的环境（目标系统）不是同一个环境。例如在Linux服务器上上通过Cmake构建出需要在ARM嵌入式设备上运行可执行文件。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

10km

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值