jpnorair / _hbsys

Package building and management tool for HB software components

HBsys: A Simple Build and Package Management Tool

HBsys (stored in directory named "_hbsys" for the purpose of ordering within a root directory) provides a makefile that works together with child makefiles from compliant software components.

The point of HBsys is to provide a build system for a group of embedded POSIX software, typically deployed together as middleware, without resorting to complicated build systems like cMake or BitBake. HBsys is not as versatile or generic as these, but it relies merely on good ol' makefiles.

Incomplete list of software that builds with HBsys:

• argtable
• bintex
• birdmon
• clithread
• cmdtab
• libotfs
• libjudy
• otter
• ottercat
• otvar
• OTEAX
• wfedd

Customization of Build & Management

The HBsys API is your text editor. It is based on simple makefiles. There is no proprietary API to learn. Just fork the project and customize it however you see fit.

Usage

There are three high-level things you can do with HBsys.

1. sys-install: Add already-built, HB-compliant packages to HBsys management (via _hbsys/makefile).
2. opt-install: Install a distribution of software programs managed by HBsys into /opt tree (via _hbsys/makefile).
3. pkg: create an HB-compliant software package (via HB-compliant software makefile)

sys-install

$ cd _hbsys
$ make sys-install

Note: make or make all alias to make sys-install

What happens here, is that all the software packaged in the _hbpkg directory (this is created by pkg operation if it doesn't already exist), and matching the system information of the local build system (e.g. Linux-4.4.0-137-generic-x86_64, Darwin-18.7.0-x86_64, etc), will get symlinked into a corresponding directory within _hbsys. You can include and link from headers and libraries, respectively, within the _hbsys hierarchy.

opt-install

$ cd _hbsys
$ make opt-install

After running sys-install, you can copy a distribution of executable software inclusive in _hbsys (i.e. the bin subdirectory) into a tree starting with /opt

pkg

$ cd __some_hb-compliant_repo__
$ make pkg

All software that builds with HBsys will contain individual, local makefiles. Running make pkg will build a package of whatever that software requires and copy it to a corresponding subdirectory within _hbpkg. It is the duty of the local makefile to specify what exactly make pkg will build (e.g. it could be a program, a library, or just a header file).