Compiling, portability, dependencies, and testing

Miller
User info:
• About
• File formats
• Miller features in the context of the Unix toolkit
• Record-heterogeneity
• Performance
• Why call it Miller?
• How original is Miller?
• Reference
• Data examples
• Things to do
Developer info:
• Compiling, portability, dependencies, and testing
• Why C?
• Contact information
• GitHub repo

I build with

gcc -std=gnu99 -Wall -Werror -O3

and I’ve done so successfully on Ubuntu 12.04 LTS, SELinux, and Darwin (MacOS Yosemite). I also use valgrind for detection of memory leaks and runtime memory-access errors.

In addition to GCC, the standard C library, and lex (all part of the Linux/Darwin distributions), Miller uses the following dependencies, which are included within the Miller source tree:

MinUnit for unit-testing, with as-is-no-warranty license http://www.jera.com/techinfo/jtns/jtn002.html#License.
The Lemon parser-generator, the author of which explicitly disclaims copyright.

Lastly, this documentation pageset is built using Poki: docs here, source code here.

Miller uses MinUnit unit-test for key classes including lrec_t. The remaining coverage (which is exhaustive) is regression coverage of Miller using all data-transform options and all I/O-format pairs.