About cspice-cmake-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/tudat-team/cspice-cmake

Package license: BSD

Summary: Mirror of SPICE Toolbox sourcecode with additional CMake files.

Current build status

Azure

Variant Status linux_64 osx_64 osx_arm64 win_64

Current release info

Name	Downloads	Version	Platforms

Installing cspice-cmake

Installing cspice-cmake from the tudat-team channel can be achieved by adding tudat-team to your channels with:

conda config --add channels tudat-team
conda config --set channel_priority strict

Once the tudat-team channel has been enabled, cspice-cmake can be installed with conda:

conda install cspice-cmake

or with mamba:

mamba install cspice-cmake

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

conda search cspice-cmake --channel tudat-team

or with mamba:

mamba search cspice-cmake --channel tudat-team

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search cspice-cmake --channel tudat-team

# List packages depending on `cspice-cmake`:
mamba repoquery whoneeds cspice-cmake --channel tudat-team

# List dependencies of `cspice-cmake`:
mamba repoquery depends cspice-cmake --channel tudat-team

Updating cspice-cmake-feedstock

If you would like to improve the cspice-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 tudat-team channel, whereupon the built conda packages will be available for everybody to install and use from the tudat-team channel. Note that all branches in the tudat-team/cspice-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:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers