About cppinterop-feedstock

Feedstock license: BSD-3-Clause

Home: https://github.com/compiler-research/CppInterOp

Package license: Apache-2.0 WITH LLVM-exception

Summary: The CppInterOp library provides a minimalist approach for other languages to interoperate with C++ entities.

Development: https://cppinterop.readthedocs.io/en/1.5.0/DevelopersDocumentation.html

Documentation: https://cppinterop.readthedocs.io/en/1.5.0

CppInterOp exposes API from Clang and LLVM in a backward compatibe way. The API support downstream tools that utilize interactive C++ by using the compiler as a service. That is, embed Clang and LLVM as a libraries in their codebases. The API are designed to be minimalistic and aid non-trivial tasks such as language interoperability on the fly. In such scenarios CppInterOp can be used to provide the necessary introspection information to the other side helping the language cross talk.

Current build status

Azure

Variant Status linux_64 linux_aarch64 linux_ppc64le osx_64 osx_arm64 win_64

Current release info

Name	Downloads	Version	Platforms

Installing cppinterop

Installing cppinterop 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, cppinterop can be installed with conda:

conda install cppinterop

or with mamba:

mamba install cppinterop

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

conda search cppinterop --channel conda-forge

or with mamba:

mamba search cppinterop --channel conda-forge

Alternatively, mamba repoquery may provide more information:

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

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

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

Troubleshooting

1. Apply this patch so you can more easily run commands inside the container (adding --privileged to the docker run args can also be useful if you want to get at proper debugging tools):

diff
diff --git a/.scripts/run_docker_build.sh b/.scripts/run_docker_build.sh
index 00f377a..245af4b 100755
--- a/.scripts/run_docker_build.sh
+++ b/.scripts/run_docker_build.sh
@@ -105,10 +105,10 @@ docker run ${DOCKER_RUN_ARGS} \
            -e STAGING_BINSTAR_TOKEN \
            "${DOCKER_IMAGE}" \
            bash \
-           "/home/conda/feedstock_root/${PROVIDER_DIR}/build_steps.sh"
+           # "/home/conda/feedstock_root/${PROVIDER_DIR}/build_steps.sh"

 # verify that the end of the script was reached
 test -f "$DONE_CANARY"

2. Run ./build-locally.py
3. Run /home/conda/feedstock_root/.scripts/build_steps.sh inside the container
4. when it fails look for a path like /home/conda/feedstock_root/build_artifacts/clad_1711986423265/ in the log
5. cd $ABOVE/test_tmp/
6. source conda_test_env_vars.sh
7. bash run_test.sh

About conda-forge

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 cppinterop-feedstock

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

• @JohanMabille
• @alexander-penev
• @vgvassilev