Updating pkg config

27 Mar

In order to provide high-quality builds, the process has been automated into the conda-forge Git Hub organization.

The conda-forge organization contains one repository for each of the installable packages. 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.

Unfortunately not all the package maintainers have set up the packages to be smart enough to make the transition from one old package to a new one so smooth.

You might have even tried to do this: If you are not logged in as root you may need to `su` into root privileges or use sudo.

The situation I have described exists since pkgng was released, since at least 2012.

I've been having a harrowing time lately just trying to get several C programs compiled because I can't find where the libraries are located and pkg-config seems to be out of order.

They represent the parameters to pass to the compiler and linker command-lines to make use of the current module.

It's important not to list the entries related to further dependencies, since has been designed to work in pair with the rest of the autotools stack, the same expansion rules apply, making it easy to deal with, as long as the previously shown example is followed.

Thanks to the awesome service provided by Circle CI, App Veyor and Travis CI it is possible to build and upload installable packages to the conda-forge Anaconda-Cloud channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions) If you would like to improve the pkg-config recipe or build a new package version, please fork this repository and submit a PR.