diff options
author | Rob Austein <sra@hactrn.net> | 2016-06-27 16:26:25 -0400 |
---|---|---|
committer | Rob Austein <sra@hactrn.net> | 2016-06-27 16:26:25 -0400 |
commit | 0f3cc3aa55bcc6476d721f9fbb8dfe8559d85ff7 (patch) | |
tree | b26632f3ff40fe79fabc07e5d63be4953ef71df9 /software/README.md | |
parent | f7aa0ad426ddfc01f66212a6c4f5cf352400faf2 (diff) |
First cut at consolidated alpha releng.
Undoubtedly doesn't work yet, and still needs doc, but perhaps now
ready for testing on build machine.
Diffstat (limited to 'software/README.md')
-rw-r--r-- | software/README.md | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/software/README.md b/software/README.md deleted file mode 100644 index 15c1006..0000000 --- a/software/README.md +++ /dev/null @@ -1,31 +0,0 @@ -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. |