aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2016-07-11 18:44:49 -0400
committerRob Austein <sra@hactrn.net>2016-07-11 18:44:49 -0400
commit3861954162e4295b44216e1ac35e37193812156c (patch)
tree7ef1d4f08329a87b9c5a6ef1afa29b607d312f0a
parent1d3045e82e4378853c2ec1ced9074e11f5ae8d4c (diff)
Oops, README.md was written before we added Homebrew support.
-rw-r--r--README.md28
1 files changed, 18 insertions, 10 deletions
diff --git a/README.md b/README.md
index 42c50a0..a099e13 100644
--- a/README.md
+++ b/README.md
@@ -104,7 +104,7 @@ current build process:
package produces a source tarball as one of its outputs, so we get
that for free by doing this step first.
-2. Running "pbuilder" to generate clean binary packages for the
+2. Running [pbuilder][] to generate clean binary packages for the
"i386" and "amd64" architectures for Debian Jessie and Ubuntu
Xenial.
@@ -114,17 +114,25 @@ current build process:
4. Uploading changes from the staging repositories to our public APT
repositories.
-Planned, but missing from the above, is generation of a Homebrew
-formula for Mac OS X and loading that formula along with the
-corresponding source tarball to a public Homebrew "tap". At least the
-initial version of this will likely be a source-only formula; in
-theory, it would be possible for us to cross-compile Mac OS X binaries
-without needing an expensive build farm (eg, using
-https://github.com/tpoechtrager/osxcross), but we haven't sorted
-through either the technical or licensing issues.
+5. Generation of a [Homebrew][] formula and committing that formula to
+ the staging instance of a Homebrew "tap" (git repository), using a
+ tarball created during the Debian source package stage as the
+ source package. The Homebrew formula is source-only (no "bottled"
+ binary packages): creating binary packages would not be
+ particularly difficult (one [osxcross][] instance per version of
+ OSX we want to support would do it), but Apple's Xcode SDK license
+ doesn't permit this unless we run our build farm on Apple
+ hardware.
In theory, it would also be possible to produce Windows binaries using
-the MinGW cross-compilation environment, but Windows is sufficiently
+the [MinGW][] cross-compilation environment, but Windows is sufficiently
different from all other platforms that even minimal Windows support
would almost certainly require extensive source code changes, so we
have not put any serious thought into build issues for Windows.
+
+
+[XiLinxTools]: http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html
+[osxcross]: https://github.com/tpoechtrager/osxcross
+[pbuilder]: https://pbuilder.alioth.debian.org/
+[Homebrew]: http://brew.sh/
+[MinGW]: http://www.mingw.org/