diff options
| author | Rob Austein <sra@hactrn.net> | 2016-06-22 15:34:57 -0400 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2016-06-22 15:34:57 -0400 |
| commit | beca9ece1b3a9f47d81b98f06fc4b0180704cabe (patch) | |
| tree | e265980b30305c60d6932cdf8b5403914a66516d /README.md | |
First cut at release engineering for software that goes with the Alpha board.
This may well end up merging with the firmware super-repository, but,
having started down the road of making them separate, let's keep it
that way while we get the initial stuff out of the way, then merge
them if it still seems like a good idea when the basics are working.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/README.md b/README.md new file mode 100644 index 0000000..15c1006 --- /dev/null +++ b/README.md @@ -0,0 +1,31 @@ +Preliminary release engineering super-repository for building software +to work with the Cryptech "Alpha" board. + +Primary task here is to build the PKCS #11 library and any needed +support tools for whichever platforms we support. This will involve +some packaging voodoo. + +Our first targets for this are Debian and Ubuntu, probably the Jessie +and Xenial releases, respectively. If we really need to support +multiple releases for each of these platforms, the packaging mechanics +become more complicated, so we may just stop here for these platforms +and assume we can fill any odd corners using the associated source +package. + +Our next target for this is likely to be Mac OS X. This should be +relatively straightforward so long as we only have to support Homebrew +and we don't have to produce Homebrew "bottles" (binary packages). If +we do need to bottle, we either need one or more Mac build machines or +we need some kind of cross-compilation scheme (eg, +https://github.com/tpoechtrager/osxcross). + +Supporting Homebrew at all requires a bit of extra voodoo on top of +supporting Debian packaging, but none of it looks particularly +difficult, and the Debian packaging will produce the source tarball we +need for the Homebrew formula, so integrating production of these two +kinds of packaging makes some sense. + +Windoze is not currently on the radar. In theory, MinGW would suffice +as a cross compiler if and when we have to do something about it. + +This README is probably obsolete by the time you're reading it. |