faster single threaded ◉ Why is it there in the first place? 27What’s a PhysFS? ◉ Open source multiplatform VFS library ◉ Mount folders, drives and archives ◉ Intended for use in video games ◉ Written

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

designed and optimized for accelerating the development and Continuous Integration of C and C++ projects. With full binary management, it can create and reuse any number of different binaries (for different to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection conan/profiles/default and defined custom values for some of them as command line arguments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch

Package consumers (client application users that are installing existing packages to reuse in their projects) will typically retrieve pre-compiled binaries for their systems in case such compatible binaries to your local user cache (typically .conan/data), and can be reused from this location for other projects. This allows to clean your current project and continue working even without network connection stored in ~/.conan/profiles/default and defined as command line argu- ments. However, in large projects, configurations can get complex, settings can be very different, and we need an easy way to switch