• About Miller • File formats • Miller features in the context of the Unix toolkit • Record-heterogeneity • Reference • Data examples • FAQ • Internationalization • Compiling, portability, dependencies, and testing • Performance • Why C? • Why call it Miller? • How original is Miller? • Things to do • Documents by release • Contact information • GitHub repo |
• Building from source • From release tarball using autoconfig • From git clone using autoconfig • Creating a release tarball • Without using autoconfig • In case of problems • Dependencies • Required external dependencies • Optional external dependencies • Internal dependencies • License Prebuilt executablesPlease see https://github.com/johnkerl/miller/releases where there are builds for OSX Yosemite, Linux i686 (statically linked), and Linux x86-64 (dynamically linked). Homebrew installation support for OSX is available via brew update && brew install miller. You may already have mlr available in your platform’s package manager on NetBSD, Debian Linux, Arch Linux, or perhaps other distributions.Building from sourceFrom release tarball using autoconfigMiller allows you the option of using GNU autoconfigure to build portably.
From git clone using autoconfig
Creating a release tarball
Without using autoconfigGNU autoconfig is familiar to many users, and indeed plenty of folks won’t bother to use an open-source software package which doesn’t have autoconfig support. And this is for good reason: GNU autoconfig allows us to build software on a wide diversity of platforms. For this reason I’m happy that Miller supports autoconfig. But, many others (myself included!) find autoconfig confusing: if it works without errors, great, but if not, the ./configure && make output can be exceedingly difficult to decipher. And this also can be a turn-off for using open-source software: if you can’t figure out the build errors, you may just keep walking. For this reason I’m happy that Miller allows you to build without autoconfig. (Of course, if you have any build errors, feel free to contact me at kerl.john.r+miller@gmail.com, — or, better, open an issue with “New Issue” at https://github.com/johnkerl/miller/issues.) Steps:
In case of problemsIf you have any build errors, feel free to contact me at kerl.john.r+miller@gmail.com, — or, better, open an issue with “New Issue” at https://github.com/johnkerl/miller/issues.DependenciesRequired external dependenciesThese are necessary to produce the mlr executable.
Optional external dependenciesThis documentation pageset is built usingInternal dependenciesThese are included within the Miller source tree and do not need to be separately installed (and in fact any separate installation will not be picked up in the Miller build):
LicenseTwo-clause BSD license https://github.com/johnkerl/miller/blob/master/LICENSE.txt. |