Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/bincrafters/conan-glibc_version_header

conan.io recipe for glibc_version_header
https://github.com/bincrafters/conan-glibc_version_header

conan conanfile glibc

Last synced: about 2 months ago
JSON representation

conan.io recipe for glibc_version_header

Awesome Lists containing this project

README

        

[![Download](https://api.bintray.com/packages/bincrafters/public-conan/glibc_version_header%3Abincrafters/images/download.svg) ](https://bintray.com/bincrafters/public-conan/glibc_version_header%3Abincrafters/_latestVersion)
[![Build Status](https://travis-ci.com/bincrafters/conan-glibc_version_header.svg?branch=testing%2F0.1)](https://travis-ci.com/bincrafters/conan-glibc_version_header)

[Conan.io](https://conan.io) package recipe for [*glibc_version_header*](https://github.com/wheybags/glibc_version_header).

Build portable Linux binaries without using an ancient distro

The packages generated with this **conanfile** can be found on [Bintray](https://bintray.com/bincrafters/public-conan/glibc_version_header%3Abincrafters).

## For Users: Use this package

### Basic setup

$ conan install glibc_version_header/0.1@bincrafters/testing

### Project setup

If you handle multiple dependencies in your project is better to add a *conanfile.txt*

[requires]
glibc_version_header/0.1@bincrafters/testing

Complete the installation of requirements for your project running:

$ mkdir build && cd build && conan install ..

Note: It is recommended that you run conan install from a build directory and not the root of the project directory. This is because conan generates *conanbuildinfo* files specific to a single build configuration which by default comes from an autodetected default profile located in ~/.conan/profiles/default . If you pass different build configuration options to conan install, it will generate different *conanbuildinfo* files. Thus, they should not be added to the root of the project, nor committed to git.

## For Packagers: Publish this Package

The example below shows the commands used to publish to bincrafters conan repository. To publish to your own conan respository (for example, after forking this git repository), you will need to change the commands below accordingly.

## Build and package

The following command both runs all the steps of the conan file, and publishes the package to the local system cache. This includes downloading dependencies from "build_requires" and "requires" , and then running the build() method.

$ conan create bincrafters/testing

### Available Options
| Option | Default | Possible Values |
| ------------- |:----------------- |:------------:|
| glibc_version | 2.12.2 | ['2.10.2', '2.11.3', '2.12.2', '2.13', '2.13.1', '2.14', '2.15', '2.16', '2.17', '2.18', '2.19', '2.20', '2.21', '2.22', '2.23', '2.24', '2.25', '2.26', '2.27', '2.5.1', '2.5', '2.6.1', '2.6', '2.7', '2.8', '2.9'] |

## Add Remote

$ conan remote add bincrafters "https://api.bintray.com/conan/bincrafters/public-conan"

## Upload

$ conan upload glibc_version_header/0.1@bincrafters/testing --all -r bincrafters

## Conan Recipe License

NOTE: The conan recipe license applies only to the files of this recipe, which can be used to build and package glibc_version_header.
It does *not* in any way apply or is related to the actual software being packaged.

[MIT]([email protected]:bincrafters/conan-glibc_version_header.git/blob/testing/0.1/LICENSE.md)