diff options
author | Rob Austein <sra@hactrn.net> | 2016-06-27 11:38:39 -0400 |
---|---|---|
committer | Rob Austein <sra@hactrn.net> | 2016-06-27 11:38:39 -0400 |
commit | 5ce361bac89d49a368350e8c475b83e8e6cf0718 (patch) | |
tree | 0ad3144eebb5f069c238b35611750fe29d2ca1ab /software/README.md | |
parent | 89e23287021da6db980ebbcca3c651bc163514bb (diff) | |
parent | 856cb22d530e820c122e0dbee5b61edff91d235e (diff) |
Merged software/master.
Diffstat (limited to 'software/README.md')
-rw-r--r-- | software/README.md | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/software/README.md b/software/README.md new file mode 100644 index 0000000..15c1006 --- /dev/null +++ b/software/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. |