conda-forge / vc-feedstock

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

About vc-feedstock

Feedstock license: BSD-3-Clause

About vc

Home: https://docs.microsoft.com/en-us/visualstudio/windows/?view=vs-

Package license: LicenseRef-ProprietaryMicrosoft

Summary: Activation and version verification of MSVC (VS compiler, update update_version)

About vc14_runtime

Home: https://visualstudio.microsoft.com/downloads/

Package license: LicenseRef-ProprietaryMicrosoft

Summary: MSVC runtimes associated with cl.exe version 19.39.33519 (VS 2022 update 9)

About vs2022_win-64

Package license: BSD-3-Clause

Summary: Activation and version verification of MSVC 14.3 (VS 2022 compiler, update 11)

About vc

Home: https://github.com/conda/conda/wiki/VC-features

Package license: BSD-3-Clause

Summary: A meta-package to impose mutual exclusivity among software built with different VS versions

Development: https://github.com/conda/conda/wiki/VC-features

Documentation: https://github.com/conda/conda/wiki/VC-features

This metapackage is used to enforce consistency of runtime dependencies within an environment

About vs2015_runtime

Home: https://github.com/conda-forge/vc-feedstock

Package license: BSD-3-Clause

Summary: A backwards compatible meta-package. See vc14_runtime for the new package.

About vs_win-64

Package license: BSD-3-Clause

Summary: Activation and version verification of MSVC 14.3 (VS 2022 compiler, update 11)

About vs2022_win-arm64

Package license: BSD-3-Clause

Summary: Activation and version verification of MSVC 14.3 (VS 2022 compiler, update 9)

About vs_win-arm64

Package license: BSD-3-Clause

Summary: Activation and version verification of MSVC 14.3 (VS 2022 compiler, update 9)

About vs2019_win-64

Package license: BSD-3-Clause

Summary: Activation and version verification of MSVC 14.2 (VS 2019 compiler, update 11)

Current build status

Azure
VariantStatus
win_64_cl_version19.29.30139cross_t_h16fbe5123a variant
win_64_cl_version19.39.33519cross_t_h0df7bd75cc variant
win_64_cl_version19.39.33519cross_t_h94575db908 variant
win_64_cl_version19.40.33808cross_t_h0d7d6ff254 variant
win_64_cl_version19.40.33808cross_t_h50d9fe5020 variant
win_64_cl_version19.41.34120cross_t_hce58adb501 variant
win_64_cl_version19.41.34120cross_t_hd9d6fca87a variant
win_arm64_cl_version19.29.30139cros_h5ab1bbeecd variant
win_arm64_cl_version19.39.33519cros_h835692272b variant
win_arm64_cl_version19.39.33519cros_h9c25a1236d variant
win_arm64_cl_version19.40.33808cros_h7173afee75 variant
win_arm64_cl_version19.40.33808cros_h98edac65ce variant
win_arm64_cl_version19.41.34120cros_hf07a69c0f6 variant
win_arm64_cl_version19.41.34120cros_hfcbbf4eb76 variant

Current release info

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

Installing vc

Installing vc 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, vc, vc14_runtime, vs2015_runtime, vs2019_win-64, vs2022_win-64, vs2022_win-arm64, vs_win-64, vs_win-arm64 can be installed with conda:

conda install vc vc14_runtime vs2015_runtime vs2019_win-64 vs2022_win-64 vs2022_win-arm64 vs_win-64 vs_win-arm64

or with mamba:

mamba install vc vc14_runtime vs2015_runtime vs2019_win-64 vs2022_win-64 vs2022_win-arm64 vs_win-64 vs_win-arm64

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

conda search vc --channel conda-forge

or with mamba:

mamba search vc --channel conda-forge

Alternatively, mamba repoquery may provide more information:

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

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

# List dependencies of `vc`:
mamba repoquery depends vc --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 vc-feedstock

If you would like to improve the vc 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/vc-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