search

conda-forge / cmake-feedstock

A conda-smithy repository for cmake.
BSD 3-Clause "New" or "Revised" License
4 stars 43 forks source link

readme

About cmake-feedstock

Feedstock license: BSD-3-Clause

About cmake

Home: http://www.cmake.org/

Package license: BSD-3-Clause

Summary: CMake is an extensible, open-source system that manages the build process

Development: https://gitlab.kitware.com/cmake/cmake

Documentation: https://cmake.org/documentation

About cmake

Home: http://www.cmake.org/

Package license: BSD-3-Clause

Summary: CMake is an extensible, open-source system that manages the build process

Development: https://gitlab.kitware.com/cmake/cmake

Documentation: https://cmake.org/documentation

Current build status

Azure
VariantStatus
linux_64 variant
linux_aarch64 variant
linux_ppc64le variant
osx_64 variant
osx_arm64 variant
win_64 variant

Current release info

Name Downloads Version Platforms
Conda Recipe Conda Downloads Conda Version Conda Platforms

Installing cmake

Installing cmake from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, cmake can be installed with conda:

conda install cmake

or with mamba:

mamba install cmake

It is possible to list all of the versions of cmake available on your platform with conda:

conda search cmake --channel conda-forge

or with mamba:

mamba search cmake --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search cmake --channel conda-forge

# List packages depending on `cmake`:
mamba repoquery whoneeds cmake --channel conda-forge

# List dependencies of `cmake`:
mamba repoquery depends cmake --channel conda-forge

About conda-forge

Powered by NumFOCUS

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating cmake-feedstock

If you would like to improve the cmake recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/cmake-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

Feedstock Maintainers