Separate into multiple stages, at least during development.

Docker is pretty clever about not rebuilding stuff, but
simply having the 6GB XiLinx tarball in the build context
is painful, so let's avoid that as much as we can.

1 files changed, 18 insertions, 0 deletions

diff --git a/stage2/Dockerfile b/stage2/Dockerfile
new file mode 100644
index 0000000..da030c8
--- /dev/null
+++ b/stage2/Dockerfile
@@ -0,0 +1,18 @@
+FROM xilinx:loadonly
+
+# Whack /bin/sh (known issue with XiLinx tools not working with /bin/dash)
+
+RUN ln -sf /bin/bash /bin/sh
+
+# Here's where it gets really fun: let's see if we can drive the
+# frelling XiLinx installation under Xvfb.  Need some tools first,
+# then some manual debugging to get the details right.  Don't expect
+# to need all of the following once we've debugged this.
+
+RUN apt-get update && apt-get install -y \
+    python-xvfbwrapper \
+    ratpoison \
+    x11-apps \
+    x11-utils \
+    x11-xserver-utils \
+    xautomation