## +24 ## Common Package Specification (CPS) in Practice: A Full Round Trip Implementation in Conan C++ Package Manager DIEGO RODRIGUEZ-LOSADA GONZALEZ  ### CONAN 2.0 C/C++ Package Manager ## Outline - Introduction to Common Package Specification (CPS) - Creation of CPS files from existing Conan packages - Loading native files from CPS - Location of CPS files - Lessons learned and conclusions ## Why a Common Package Specification (CPS) C/C++ projects top 4 pains: Managing libraries Build times Setting CI Managing

A Common Package Specification: Getting Build Tools to Talk to Each Other: Lessons Learned From Making Thousands of Binaries Consumable by Any Build System DIEGO RODRIGUEZ-LOSADA GONZALEZ  ### CONAN 2.0 C/C++ Package Manager ## Outline - Definition and scope - Implementation experience - CPS basics - Directories configuration: Windows, x86_64, VS-2022, Release, static library 3. Install (system package manager or language package manager), build from source by the user, with that configuration 4. Pass information

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 integrations 10 2.5 New custom user commands 10 2.6 New CLI 10 2.7 New deployers 10 2.8 New package_id 11 2.9 compatibility.py 11 2.10 New lockfiles 11 2.11 New configuration and environment 11 2.12 Multi-revision cache 12 2.13 New extensions plugins 12 2.14 Package immutability optimizations 12 2.15 Package lists 13 2.16 Metadata files 13 2.17 Third party backup sources 13 2

welcome 9 Python Module Index 761 Index 765 Welcome to conda's documentation! Conda provides package, dependency, and environment management for any language. Here, you will find everything you need 4.1 User guide #### 4.1.1 Getting started with conda Conda is a powerful command line tool for package and environment management that runs on Windows, macOS, and Linux. This guide to getting started Conda allows you to create separate environments, each containing their own files, packages, and package dependencies. The contents of each environment do not interact with each other. The most basic way

Using Lean Online 1 1.2 Using Lean with VSCode 1 1.3 Using Lean with Emacs 2 1.4 Using the Package Manager 3 2 Lexical Structure 7 2.1 Symbols and Commands 7 2.2 Identifiers 7 2.3 String Literals justify. #### 1.2.2 Multi-file Projects If you want to work on a project with multiple files, use the package_manager to set up a project folder, and then use Open Folder in the VSCode File menu to open the in this case, the type of the identity function. #### 1.3.1 Features Lean mode uses an Emacs package named Flycheck, as evidenced by the letters FlyC that appear in the information line. Flycheck offers

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 Defining Package ABI Compatibility ..... 61 7.7 Define the package information ..... 74 7.8 Toolchains ..... 77 7.9 Inspecting Packages ..... 78 7.10 Packaging Approaches ..... 79 7.11 Package Creator Developing packages ..... 101 9.1 Package development flow ..... 101 9.2 Package layout ..... 106 9.3 Packages in editable mode ..... 111 9.4 Workspaces ..... 116 10 Package apps and devtools ..... 123

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 73 7.6 Defining Package ABI Compatibility 75 7.7 Define the package information 88 7.8 Toolchains 91 7.9 Inspecting Packages 92 7.10 Packaging Approaches 93 7.11 Package Creator Tools 97 103 9 Developing packages 111 9.1 Package development flow 111 9.2 Package layout 116 9.3 Packages in editable mode 127 9.4 Workspaces 130 10 Package apps and devtools 137 10.1 Running and

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 57 7.6 Defining Package ABI Compatibility 59 7.7 Define the package information 72 7.8 Toolchains 75 7.9 Inspecting Packages 76 7.10 Packaging Approaches 77 7.11 Package Creator Tools 82 92 9 Developing packages 99 9.1 Package development flow 99 9.2 Package layout 104 9.3 Packages in editable mode 113 9.4 Workspaces 116 10 Package apps and devtools 123 10.1 Running and

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 6 Defining Package ABI Compatibility 47 6.7 Define the package information 61 6.8 Toolchains ..... 63 6.9 Inspecting Packages ..... 73 6.10 Packaging Approaches ..... 74 6.11 Package Creator Tools 87 8 Developing packages ..... 93 8.1 Package development flow ..... 93 8.2 Packages in editable mode ..... 98 8.3 Workspaces ..... 102 9 Package apps and devtools ..... 109 9.1 Running and

Powered by TCPDF (www.tcpdf.org) ## CONTENTS 1 Introduction 3 1.1 Open Source 3 1.2 Decentralized package manager 3 1.3 Binary management 4 1.4 All platforms, all build systems and compilers 5 1.5 5.6 Defining Package ABI Compatibility 45 5.7 Define the package information 58 5.8 Toolchains 61 5.9 Inspecting Packages ..... 66 5.10 Packaging Approaches ..... 66 5.11 Package Creator Tools . 79 7 Developing packages ..... 85 7.1 Package development flow ..... 85 7.2 Packages in editable mode ..... 90 7.3 Workspaces ..... 94 8 Package apps and devtools ..... 101 8.1 Running and