11 docs tagged with "advanced"

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

The following guides cover topics specific to building packages for Windows on conda-forge.

Windows recipes rely on CMD/Batch scripts (.bat) by default.

In order to compile native code (C, C++, etc.) on Windows, you will need to

conda-forge has access to external CI resources that can provide GPU-equipped and/or long-running builds (beyond the usual 6h limit).

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.

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!).

Sometimes you face the possibility of needing to package a fork.

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.

Some packages maintain both an Autotools build and a CMake build. Some maintainers

The first thing that you should know is that you can locally test Windows