docs.conan.io

• charset: utf-8
• name: viewport content: width=device-width, initial-scale=1
• name: viewport content: width=device-width, initial-scale=1.0

• http://docs.conan.io/#
• Next
• Installation
• Tutorial
• CI Tutorial
• Devops guide
• Security
• Integrations
• Examples
• Reference
• Knowledge
• Incubating features
• What’s new in Conan 2
• Changelog
• Click here to read the
• ¶
• Consuming packages
• Creating packages
• Working with Conan repositories
• Developing packages locally
• Versioning
• Other important Conan features
• Project setup
• Packages pipeline
• Products pipeline
• Using ConanCenter packages in production environments
• Local Recipes Index Repository
• Backing up third-party sources with Conan
• Managing package metadata files
• Versioning
• Save and restore packages from/to the cache
• Vendoring dependencies in Conan packages
• Package promotions
• Checking package vulnerabilities
• Package compression format
• Scanning dependencies with
• Software Bills of Materials (SBOM)
• Security guidelines
• C, C++ Compiler Sanitizers
• CMake
• CLion
• Visual Studio
• Autotools
• Bazel
• Makefile
• Xcode
• Meson
• Emscripten
• Premake
• Android
• JFrog
• ROS
• GitHub
• Community
• ConanFile methods examples
• Conan extensions examples
• Conan recipe tools examples
• Cross-building examples
• Configuration files examples
• Graph examples
• Developer tools and flows
• Conan commands examples
• Conan runners examples
• Conan security examples
• Binary model
• Commands
• conanfile.py
• conanfile.txt
• Conan Server
• Configuration files
• Environment variables
• Extensions
• Recipe tools
• Runners
• Workspace files
• Cheat sheet
• Core guidelines
• FAQ
• Videos
• JFrog Academy: Conan 2 Training
• Community Resources
• 2.25
• 2.24
• 2.23
• 2.22
• 2.21
• 2.20
• 2.19
• 2.18
• 2.17
• 2.16
• 2.15
• 2.14
• 2.13
• 2.12
• 2.11
• 2.10
• 2.9
• 2.8
• 2.7
• 2.6
• 2.5
• 2.4
• 2.3
• 2.2
• 2.1
• 2.0
• 2
• 1
• 1.66
• 1.65
• 1.64
• 1.63
• 1.62
• 1.61
• 1.60
• 1.59
• 1.58
• 1.57
• 1.56
• 1.55
• 1.54
• 1.53
• 1.52
• 1.51
• 1.50
• 1.49
• 1.48
• 1.47
• 1.46
• 1.45
• 1.44
• 1.43
• 1.42
• 1.41
• 1.40
• 1.39
• 1.38
• 1.37
• 1.36
• 1.35
• 1.34
• 1.33
• 1.32
• 1.31
• 1.30
• 1.29
• 1.28
• 1.27
• 1.26
• 1.25
• 1.24
• 1.23
• 1.22
• 1.21
• 1.20
• 1.19
• 1.18
• 1.17
• 1.16
• 1.15
• 1.14
• 1.13
• 1.12
• 1.11
• 1.10
• 1.9
• 1.8
• 1.7
• 1.6
• 1.5
• 1.4
• 1.3
• PDF

• Essentials
• Advanced
• Edit on GitHub
• Conan home page
• Github project and issue tracker

            Domain Name: CONAN.IO 
Registry Domain ID: 5f58de360e96442fbc17d9389468fdd1-DONUTS 
Registrar WHOIS Server: whois.name.com 
Registrar URL: http://www.name.com 
Updated Date: 2026-05-16T16:36:31Z 
Creation Date: 2015-06-03T10:05:15Z 
Registrar Registration Expiration Date: 2027-06-03T10:05:15Z 
Registrar: Name.com, Inc. 
Registrar IANA ID: 625 
Reseller:  
Please visit https://www.nic.io/whois-search.htm for more info.
The data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. does not guarantee its accuracy.  Users accessing the Name.com, Inc. WHOIS service agree to use the data only for lawful purposes, and under no circumstances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Name.com, Inc., except as reasonably necessary to register domain names or modify existing registrations. When using the Name.com, Inc. WHOIS service, please consider the following: the WHOIS service is not a replacement for standard EPP commands to the SRS service. WHOIS is not considered authoritative for registered domain objects. The WHOIS service may be scheduled for downtime during production or OT&E maintenance periods. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements.  Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis, for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at [www.name.com/whois-layered-access] Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
        

Техническо SEO

SEO на страницата

Съдържание и UX