BD

Simple (to use), one-file build tool for C/C++ projects.

What does it do?

• It's a simple build tool for C/C++ projects
• Its instructions on what to build are directly stored within the source code itself (included as a header file), making it compact
• You can choose between four different build types
• It makes sure to recompile a file if their dependency (either header file or library) was modified

How to use

1. Clone this repository into a folder
2. Add that folder to your PATH (what's that?)
3. (Optional) In your project, create a bd.conf (see configuration)
4. Run bd in your project

Help / command line interface

To see a list of all available commands and their description, run ./bd -h. Most important commands:

• build build the projects (providing no arguments defaults to this)
• clean clean the mess
• clean build basically rebuild

Colors

Following colors were picked depending on the action:

• blue = compiling
• yellow = linking
• green = up to date
• magenta = cleaning

How to configure

Have a bd.conf file in your root project, where you would normally put your Makefiles.

• This file should / will be included in bd.c as CONFIG.
• If you use bd.bat (Windows) or bd (Linux etc.) the above is handled automatically.

Types of projects (Prj::type)

• BUILD_APP builds an executable
• BUILD_STATIC builds a static library
• BUILD_SHARED builds a shared library
• BUILD_EXAMPLES same as app, but it links each specified file

Name of the project (Prj::name)

String of your output file (without extension).

• If you're building a library, precede the name with lib
• If you're building examples, the name is treated as a folder name instead
• For applications, if it's null it defaults to a

Object directory (Prj::objd)

In this folder all the object (.o) and dependency (.d) files will be dumped.

Source files (Prj::srcf)

String-array of source files necessary to successfully compile and link the project together. It's recommended to only use * and ? when pattern matching to support all operating systems.

C compile flags (Prj::cflgs)

String with your own flags. It's recommended to always at least include -Wall.

Linker options (Prj::lopts)

String with your own linker options.

Linker libraries (Prj::llibs)

String with your own linker libraries.

• Precede paths with the -L= flag. (make sure to include the equals sign)
• precede names with the -l= flag. (make sure to include the equals sign)

C compiler (Prj::cc)

String specifying C compiler to use.

• If it's null it defaults to gcc

C++ compiler (Prj::cxx)

String specifying C++ compiler to use.

• If it's null it defaults to g++

Minimum Recommended Configuration

C

/* file: `bd.conf` */
{
    .type = BUILD_APP,
    .name = "app_name",
    .objd = "obj",
    .srcf = D("src/*.c"),
    .cflgs = "-Wall -O2",
}

C++

/* file: `bd.conf` */
{
    .type = BUILD_APP,
    .name = "app_name",
    .objd = "obj",
    .srcf = D("src/*.cpp"), /* .cpp or .cc both work */
    .cflgs = "-Wall -O2",
}

Multiple different files

See https://github.com/rphii/Rlib where I created a library and used it to link with examples.

Minimum Possible Configuration

C

{.srcf = D("*.c")}

Tested platforms

• Windows
• Cygwin
• Linux
• (...missing verification for the rest...)

General Notice

• Don't have any spaces in any of the files having any business with this build tool
• If you use subfolders in the config, always use / and not \, even on Windows
• Among others, Prj::name and Prj::obj can be a sequence of subfolders

Planned

• maybe multithreading
• verify if it works other platforms