Skip to main content

18 docs tagged with "advanced"

View all tags

Advanced

The following how-to guides are available in this category:

Build NVIDIA CUDA packages

The following guides cover building conda-forge packages that depend on the CUDA Toolkit. They assume familiarity with writing recipes for compiled code (see Compilers and Runtimes) and with the user guide for running CUDA code.

Building Against NumPy

Finding numpy.get_include() in setup.py, numpy in build-system.requires of pyproject.toml, dependency('numpy') in meson.build, or cimport statements in .pyx or .pyd files are a telltale sign that the package links against NumPy.

How to build on GPU runners

By default, provisioned CI machines do not feature a GPU. See how to configure self-hosted runners if your feedstock needs access to additional resources like GPUs or long-running builds, and how to distinguish CPU and GPU jobs when your recipe builds both.

How to configure self-hosted runners

conda-forge has access to additional CI resources for feedstocks that can't build their packages in the default runners. Check Reference> Runners for a comprehensive list.

How to enable additional architectures

By default, feedstocks are created with support for the main platforms (e.g. linux-64, osx-64, win-64). Additional ones may be available in an opt-in fashion. The configuration can be changed manually in conda-forge.yml, or through automated migrations.

How to maintain several versions

The conda-forge workflow assumes that a push to any branch in the feedstock repository will result in a build being uploaded to the conda-forge channel (and that's why PRs must always be opened from a fork!).

How to talk to the bots

Some parts of the conda-forge automation are exposed as "bot commands" that can be invoked from issue titles and comments. You can check the full list in the admin-web-services documentation.

Run package tests off CI

Despite having a successful build, sometimes we can't run all the tests we'd like on CI. Some reasons include: