| 1 |
History of TriBITS |
| 2 |
------------------ |
| 3 |
|
| 4 |
TriBITS started development in November 2007 as a set of helper macros to |
| 5 |
provide a CMake build system for a small subset of packages in Trilinos. The |
| 6 |
initial goal was to support a native Windows build (using Visual C++) to |
| 7 |
compile and install these few Trilinos packages on Windows for usage by |
| 8 |
another project (the Sandia Titan project which included VTK). At that time, |
| 9 |
Trilinos was using a highly customized and augmented autotools build system. |
| 10 |
Initially, this CMake system was just a set of macros to streamline creating |
| 11 |
executables and tests. Some of the conventions started in that early effort |
| 12 |
(e.g. naming conventions of variables and macros where functions use upper |
| 13 |
case like old FORTRAN and variables are mixed case) were continued in later |
| 14 |
efforts and are reflected in the current implementation. Then, stating in |
| 15 |
early 2008, a more detailed evaluation was performed to see if Trilinos should |
| 16 |
switch over to CMake as the default (and soon only) supported build and test |
| 17 |
system (see "Why CMake?" in `TriBITS Overview`_). This lead to the initial |
| 18 |
implementation of a scalable package-based architecture (PackageArch) for the |
| 19 |
Trilinos CMake project in late 2008. This Trilinos CMake PackageArch system |
| 20 |
evolved over the next few years with development in the system slowing |
| 21 |
into 2010. This Trilinos CMake build system was then adopted as the build |
| 22 |
infrastructure for the CASL VERA effort in 2011 where CASL VERA packages were |
| 23 |
treated as add-on Trilinos packages (see Section `Multi-Repository Support`_). |
| 24 |
Over the next year, there was significant development of the system to support |
| 25 |
larger multi-repo projects in support of CASL VERA. That lead to the decision |
| 26 |
to formally generalize the Trilinos CMake PackageArch build system outside of |
| 27 |
Trilinos and the name TriBITS was formally adopted in November 2011. Work to |
| 28 |
refactor the Trilinos CMake system into a general reusable stand-alone |
| 29 |
CMake-based build system started in October 2011 and an initial implementation |
| 30 |
was complete in December 2011 when it was used for the CASL VERA build system. |
| 31 |
In early 2012, the ORNL CASL-related projects Denovo and SCALE (see [`SCALE, |
| 32 |
2011`_]) adopted TriBITS as their native development build systems. Shortly |
| 33 |
after, TriBITS was adopted as the native build system for the CASL-related |
| 34 |
University of Michigan code MPACT. In addition to being used in CASL, all of |
| 35 |
these codes also had a significant life outside of CASL. Because they used |
| 36 |
the same TriBITS build system, it proved relatively easy to keep these various |
| 37 |
codes integrated together in the CASL VERA code meta-build. At the same time, |
| 38 |
TriBITS well served the independent development teams and non-CASL projects |
| 39 |
independent from CASL VERA. Since the initial extraction of TriBITS from |
| 40 |
Trilinos, the TriBITS system was further extended and refined, driven by CASL |
| 41 |
VERA development and expansion. Independently, an early version of TriBITS |
| 42 |
from 2012 was adopted by the LiveV |
| 43 |
project (see [`LiveV`_]) which was forked and extended |
| 44 |
independently. |