Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Installing both C++ API and Python bindings

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
cmake, cpp, python
领域
build-system

调研方向

从第 55-112 行的顶层 CMakeLists.txt 开始,并配置一个启用 OTIO_CXX_INSTALL=ON 和 OTIO_PYTHON_INSTALL=ON 的构建。比较 wheel 和 non-wheel 构建中 libopentime.so、libopentimelineio.so 以及 Python wrapper DSO 的安装位置。完成的标准是,预期的区别和由此产生的安装布局已经达成一致并得到验证。

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

描述

I am creating a Conan recipe for OTIO for the aswf-docker project and I want to build and install both the C++ and Python APIs. I believe this means configuring with:

-DOTIO_CXX_INSTALL=ON
-DOTIO_PYTHON_INSTALL=ON

At lines 55-112 of the top level CMakeLists.txt, if OTIO_PYTHON_INSTALL is set, libopentime.so and libopentimelineio.so end up getting installed somewhere like /usr/local/lib/python3.13/site-packages/opentimelineio/

This may be surprising for C++ clients which would expect to find libopentime.so and libopentimelineio.so in /usr/local/lib/.

I can see how when building a Python wheel, it would be advantageous to package both the C++ DSOs as well as the pybind11 wrapper DSOs in the same place, but for a non-wheels build, it seems it would be preferable to have the C++ DSOs end up in /usr/local/lib and have the pybind11 wrapper DSOs link against those, either relying on rpath or LD_LIBRARY_PATH.

Should there be (or is there) a mechanism which would differentiate a build for the purposes of creating a Python wheel from a non wheel build?

主要语言
C++
星标
2k
派生
356
平均合并
4 天 14 小时
30 天内合并 PR
7

环境准备

从这里开始

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

AcademySoftwareFoundation/OpenTimelineIO 的其他 Issue

查看 AcademySoftwareFoundation/OpenTimelineIO 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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