blocks|key|386446|text|尝试添加-DPYTHON_EXECUTABLE:FILEPATH=/path/to/python2.7它可能是路径问题吗？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|386447|还可以指定python库的路径，使用您想要的版本：|386448|+cmake+-DPYTHON_LIBRARIES=/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib+.|code-block|syntax|javascript|386449|entityMap^0|4|1B|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Try to add <code>-DPYTHON_EXECUTABLE:FILEPATH=/path/to/python2.7</code>
It might be a path problem?

Also could specify the path to your python library,use your version that you want: 

<pre><code> cmake -DPYTHON_LIBRARIES=/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib .
</code></pre>

blocks|key|1706155|text|我也遇到了类似的问题，并使用保罗的回答作为提示解决了问题。我需要使用python2.7来编译一个旧的库，但是cmake一直在收集我的python3.2库(和可执行文件)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1706156|首先，我使用默认选项运行cmake，然后编辑它生成的CMakeCache.txt文件。我这样做主要是因为我不知道正确的-D...咒语会导致cmake获得python库并包含路径等等。|1706157|在我的CmakeCache.txt中，我发现了这样的线条|1706158|程序的路径
PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python|unordered-list-item|1706159|指向目录的路径
PYTHON_INCLUDE_DIR:PATH=/usr/include/python3.2|1706160|通向库的路径
PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython3.2.so|1706161|并将python3.2的每次发生替换为python2.7。我还必须重命名PYTHON_EXECUTABLE以使用python2.7，因为python是到系统上python3.2的一个符号链接。|1706162|然后我重新运行cmake。由于它更喜欢缓存的值，而不是实际查找库，所以在所有情况下都应该这样做。至少在我身上是这样的。|1706163|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/15291663/712526^0|Y|9|1I|5|1U|9|E|5|0|0|C|5|Q|E|1N|5|1X|5|0|3|E|0|0|0|0|2|9|J|9|10|H|1K|9|1W|6|27|9|0|7|5|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|F|3|G|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1O|8|@]|D|@]|E|$]]|$1|M|3|N|5|L|7|1P|8|@]|D|@]|E|$]]|$1|O|3|P|5|L|7|1Q|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|24|8|@$9|25|A|26|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

I had a similar problem, and resolved it using <a href="https://stackoverflow.com/a/15291663/712526">Paul's answer</a> as a hint. I needed to use <code>python2.7</code> to compile an older library, but <code>cmake</code> keeps picking up my <code>python3.2</code> libraries (and executable).

First, I ran <code>cmake</code> with default options, then edited the <code>CMakeCache.txt</code> file which it generated. I did it this way primarily because I didn't know the proper <code>-D...</code> incantations to cause <code>cmake</code> to get the python library and include paths, etc right in the first place.

In my <code>CmakeCache.txt</code>, I found lines like this

<ul>
<li>Path to a program

<pre><code>PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python
</code></pre></li>
<li>Path to a directory

<pre><code>PYTHON_INCLUDE_DIR:PATH=/usr/include/python3.2
</code></pre></li>
<li>Path to a library

<pre><code>PYTHON_LIBRARY:FILEPATH=/usr/lib/libpython3.2.so
</code></pre></li>
</ul>

And replaced every occurrence of <code>python3.2</code> with <code>python2.7</code>. I also had to rename the <code>PYTHON_EXECUTABLE</code> to use <code>python2.7</code>, since <code>python</code> is a symlink to <code>python3.2</code> on my system.

Then I reran <code>cmake</code>. Because it prefers its cached values to actually looking for the libraries, this should work in all cases. At least, it did in mine.

blocks|key|386505|text|您可以根据需要尝试这两种方法中的一种：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|386506|对于CMake+>=+3.12|offset|length|style|CODE|386507|根据变化量g：|386508|新的"FindPython3“和"FindPython2”模块，以及新的
"FindPython“模块已被添加，以提供一种新的定位方法。
python环境。|blockquote|386509|find_package(Python+COMPONENTS+Interpreter+Development)|code-block|syntax|javascript|386510|文档|386511|这个模块看起来最好是Python的第3版。如果找不到，则搜索版本2。要管理Python的并发版本3和2，请使用FindPython3和FindPython2模块而不是这个模块。|386512|对于CMake+<+3.12|386513|386514|find_package(PythonInterp+2.7+REQUIRED)
find_package(PythonLibs+2.7+REQUIRED)|386515|entityMap|0|LINK|mutability|MUTABLE|url|https://cmake.org/cmake/help/latest/module/FindPython.html#module:FindPython|1|https://cmake.org/cmake/help/v3.12/module/FindPythonInterp.html^0|0|2|D|0|0|0|0|0|2|0|0|0|2|C|0|0|2|1|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1F|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1G|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|T|3|U|5|L|7|1L|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1M|8|@$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|X|3|S|5|6|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|Y|3|Z|5|O|7|1T|8|@]|9|@]|A|$P|Q]]|$1|10|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

You may try either of these depending on what you need:

<h2>For <code>CMake &gt;= 3.12</code></h2>

According to the changelog:

<blockquote>
 New "FindPython3" and "FindPython2" modules, as well as a new 
 "FindPython" module, have been added to provide a new way to locate 
 python environments.
</blockquote>

<pre><code>find_package(Python COMPONENTS Interpreter Development)
</code></pre>

<a href="https://cmake.org/cmake/help/latest/module/FindPython.html#module:FindPython" rel="noreferrer">Docs</a>:

<blockquote>
 This module looks preferably for version 3 of Python. If not found,
 version 2 is searched. To manage concurrent versions 3 and 2 of
 Python, use FindPython3 and FindPython2 modules rather than this one.
</blockquote>

<h2>For <code>CMake &lt; 3.12</code></h2>

<a href="https://cmake.org/cmake/help/v3.12/module/FindPythonInterp.html" rel="noreferrer">Docs</a>:

<pre><code>find_package(PythonInterp 2.7 REQUIRED)
find_package(PythonLibs 2.7 REQUIRED)
</code></pre>

blocks|key|2495356|text|我使用anaconda(python+2.7.8)和python+2.7.6。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2495357|我尝试了-DPYTHON_EXECUTABLE:FILEPATH=$ANACONDA_HOME/bin，但是Version1.4发现了(奇怪的：)。|offset|length|style|CODE|2495358|我的解决方案是将其更改为PYTHON_EXECUTABLE：|2495359|cmake+-D+CMAKE_BUILD_TYPE=RELEASE+-D+CMAKE_INSTALL_PREFIX=/usr/local+-DBUILD_TIFF=ON+\
-DPYTHON_LIBRARY=$ANACONDA_HOME/lib/libpython2.7.so+\
-DPYTHON_INCLUDE_DIR=$ANACONDA_HOME/include/python2.7/+\
-DPYTHON_EXECUTABLE=$ANACONDA_HOME/bin/python|code-block|syntax|javascript|2495360|entityMap^0|0|4|1B|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|V|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I use anaconda(python 2.7.8) as well as python 2.7.6.

I tried <code>-DPYTHON_EXECUTABLE:FILEPATH=$ANACONDA_HOME/bin</code>, but version 1.4 found (weird:).

My solution is changing it to PYTHON_EXECUTABLE:

<pre><code>cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -DBUILD_TIFF=ON \
-DPYTHON_LIBRARY=$ANACONDA_HOME/lib/libpython2.7.so \
-DPYTHON_INCLUDE_DIR=$ANACONDA_HOME/include/python2.7/ \
-DPYTHON_EXECUTABLE=$ANACONDA_HOME/bin/python
</code></pre>

blocks|key|1706324|text|我的用例是一个相当大的项目，其中C%2B%2B类通过Boost.Python提供给Python脚本。在克服了CMake的Python解释器和库检测的各种怪癖之后，我终于放弃了自己的想法。我的方法是基于一个稍微经过编辑的python-config脚本的版本，这个版本有时是(但不是总是！)放入一个新创建的虚拟环境(针对这些问题的pyvenv，但我回避了)。这个脚本是由一个小的CMake片段pyconfig.cmake调用的。这两种产品都可以从GitHub回购cmake-python-config免费获得。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1706325|警告:脚本假定您的PATH中有一个Python3解释器。未尝试检测Python+2。脚本也不会尝试查找所有已安装的Python3版本。|1706326|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/42020937/why-pyvenv-does-not-install-python-config/48946977#48946977|1|https://github.com/aaszodi/cmake-python-config^0|M|C|2X|D|4F|6|5A|E|4F|6|0|69|J|1|0|9|4|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]|$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

My use case was a rather large project in which C++ classes were made available to Python scripts via <code>Boost.Python</code>. After having fought the various quirks of CMake's Python interpreter and library detection, I finally gave up and rolled my own. My approach is based on a slightly after-edited version of the <code>python-config</code> script that is sometimes (but not always!) put into a newly created virtual environment (<a href="https://stackoverflow.com/questions/42020937/why-pyvenv-does-not-install-python-config/48946977#48946977">see this SO post on <code>pyvenv</code></a> for these issues, but I digress). This script is invoked by a small CMake snippet <code>pyconfig.cmake</code>. Both are freely available from the GitHub repo <a href="https://github.com/aaszodi/cmake-python-config" rel="nofollow noreferrer">cmake-python-config</a>. 

Warning: The scripts assume that you have a Python 3 interpreter in your <code>PATH</code>. Detection of Python 2 is not attempted. The scripts do not attempt to find all installed versions of Python3 either.

I have 2 versions of python installed, but cmake is using older version. How do I force cmake to use the newer version?

I have 2 versions of python installed, but cmake is using older version. How do I force cmake to use the newer version?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我安装了两个版本的python，但是cmake使用的是旧版本。如何强制cmake使用更新版本？

问我安装了两个版本的python，但cmake使用的是旧版本。如何强制cmake使用更新版本？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我安装了两个版本的python，但cmake使用的是旧版本。如何强制cmake使用更新版本？EN