conda-forge / conda-forge/conda-forge.github.io

Document the standard practice for `lib`, `lib-dev`, and `lib-static` packages

未关闭
#1,897 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Docs enhancement
主要语言
JavaScript
星标
170
派生
320
平均合并
2 天 10 小时
30 天内合并 PR
5

描述

### Where should the content be added?

_No response_

### What should be added?

Every time I encounter this discussion it gets me, and given the same discussions scattered everywhere (ex: [here](https://github.com/conda-forge/staged-recipes/pull/21901#issuecomment-1415931866) and [here](https://github.com/conda-forge/openblas-feedstock/issues/134#issuecomment-1083482954)) I assume it's worth documenting the Linux distro practice:
- `lib`: Only the runtime shared library `libxyz.so.X` & `libxyz.so.X.Y.Z`
- `lib-dev`: Symlinks to the shared library, `libxyz.so`, plus the library headers
- `lib-static`: Contains the static libraries `libxyz.a` or `libxyz_static.a`

There may be other subtle changes needed (ex: `run_exports`). Feel free to add more details and formalize this for conda-forge needs.

### Additional information

_No response_

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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