How do I install and set up fips for a new C++ project?

Installation involves cloning the fips repository and following the external docs at floooh.github.io/fips/docs/getstarted/, which includes Python setup and initial project configuration, but this external dependency can be a barrier for quick starts.

fips vs CMake: which is better for cross-platform C++ development?

fips abstracts over CMake and other build tools, offering a simpler interface for multi-platform builds, but CMake has a larger ecosystem and community, making it more suitable for projects needing extensive third-party integration or tooling.

Can fips handle precompiled libraries like libcurl?

Yes, fips supports precompiled libraries through fipsified wrappers, as seen with libcurl in the README list, but this requires finding or creating a compatible wrapper, which may not be available for all libraries.

How to add a custom dependency not listed in the fipsified projects?

You need to create a fipsified wrapper project yourself, which involves writing configuration files to integrate the dependency, adding complexity compared to more automated dependency managers.

Is fips suitable for embedded systems with cross-compilation?

Yes, fips supports cross-compilation and multi-platform builds, making it a good fit for embedded systems, but the limited ecosystem may require more manual work for niche hardware or libraries.

What are the performance overheads of using fips?

fips adds a Python layer on top of native build tools, which can introduce minor overhead in build times, but the main trade-off is the abstraction complexity rather than significant performance hits.

Open-Awesome

fips

MITPython

A Python-based high-level build system wrapper for distributed, multi-platform C/C++ projects.

GitHub

506 stars86 forks0 contributors

What is fips?

fips is a high-level build system wrapper written in Python specifically for C/C++ projects. It simplifies the process of building and managing complex C/C++ applications across multiple platforms and distributed environments by providing a unified interface over various underlying build tools.

Target Audience

C/C++ developers working on multi-platform projects, teams managing distributed codebases, and anyone needing consistent build processes across different operating systems and architectures.

Value Proposition

Developers choose fips because it abstracts away the complexity of platform-specific build configurations and dependency management, providing a consistent workflow for building C/C++ projects regardless of the underlying operating system or build tools.

Overview

High-level build system for distributed, multi-platform C/C++ projects.

Use Cases

Best For

Managing C/C++ projects that need to build on multiple operating systems
Handling external library dependencies in C/C++ projects
Building distributed C/C++ applications spread across repositories
Simplifying cross-compilation workflows for C/C++ code
Creating consistent build processes across development teams
Abstracting away differences between various C/C++ build systems

Not Ideal For

Projects targeting a single operating system without cross-compilation needs
Small personal projects with minimal or no external dependencies
Teams already standardized on CMake with extensive tooling and community plugins
Environments where Python is not installed or where build systems must be pure C/C++ tools

Pros & Cons

Pros

Multi-platform Build Abstraction

Provides a unified interface across different operating systems and architectures, abstracting away platform-specific build details, which simplifies cross-compilation workflows.

Dependency Management

Handles external libraries through fipsified wrapper projects, reducing the complexity of integrating dependencies like bgfx or zlib into C/C++ builds.

Distributed Project Support

Supports projects spread across multiple repositories, making it easier to manage and build complex, modular codebases without manual coordination.

Build Tool Consistency

Offers a consistent workflow over various underlying build systems, minimizing the need to learn and configure different tools for each platform.

Cons

Limited Ecosystem

The README marks the list of fipsified projects as 'OBSOLETE', indicating a potentially small or outdated collection of pre-integrated libraries, which can increase setup time for new dependencies.

Python Dependency

Requires Python as a runtime dependency for C/C++ builds, which may add overhead or complexity in environments focused purely on native code without Python tooling.

External Documentation

Key documentation and install instructions are hosted externally on a separate site, making it less accessible and potentially harder to maintain compared to integrated docs.

Frequently Asked Questions

Related Projects

vcpkg

C++ Library Manager for Windows, Linux, and MacOS

a small build system with a focus on speed

Stars13,319

Forks1,848

Last commit5 days ago

conan

Conan - The open-source C and C++ package manager

Stars9,544

Forks1,134

Last commit16 hours ago

cpm

📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.

Stars4,148

Forks225

Last commit29 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub