Split package into development and runtime packages - Githubissues

conda-forge / hpx-feedstock

A conda-smithy repository for hpx.

BSD 3-Clause "New" or "Revised" License

0 stars 3 forks source link

Split package into development and runtime packages #2

Open kordejong opened 1 year ago

kordejong commented 1 year ago

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue

Packages that depend on HPX require:

An HPX development package, containing headers, static libraries, etc, to make it possible to build a Conda package.
An HPX runtime package, containing shared libraries, etc, to make it possible to use the dependent package.

In the majority of cases, users of dependent packages don't need the development files to be installed. In fact, this is against the guidelines of Conda-Forge: https://github.com/conda-forge/cfep/blob/main/cfep-18.md

Installed packages

Environment info

kordejong commented 1 year ago

@hkaiser Does HPX support installing only the runtime files (shared libraries, plugins, executables, scripts)? Is there an install target for that? No header files, static libraries, CMake scripts, and import libraries should be installed.