LIBRA (Luigi buIld Reusable Automation)

Motivation

• No existing C/C++/CUDA build system supported automatic file discovery like make via globs.

• No existing C/C++/CUDA build system provided 100% reusability across projects (assuming some conventions for file naming, directory layout, etc.). I found myself frequently copying and pasting CmakeLists.txt (or whatever the tool’s configuration was) between projects, as I added and when I find a new flag I want to add, or a new static analysis checker, etc., I would have to go and add it to EVERY project.

• No existing C/C++/CUDA build systems supported doing things like running one or more static analyzers on a repository, formatting the repository, building and running tests, etc., using make check, make format, or make tests, or other simple cmdline syntax.

This documentation has two parts: How to use LIBRA and software development guides, each detailed below.

How To Use LIBRA

• Quickstart
• Requirements to use LIBRA
• LIBRA Capabilities
• How To Hook Into LIBRA

Software Development Resources

• High-Level Architectural Guide
• OOP Software Design Principles And Patterns
• Core Development Guide
• C Development Guide
• C++ Development Guide
• Python Development Guide
• CUDA Development Guide
• Git Usage Guide
• Git Commit Guide
• Github Issues Usage Guide
• ld/Linker Script Development Guide
• General Development Workflow
• Helpful Links
• Bazel Resources