X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=version.h;h=26242ad6d9e368ec4526112f0c10fba7bcd20c34;hb=1266ac0e304b4e4db809eb045b8ac5dc43f299c4;hp=a9fab69248f0ebfec5390097d09ac1a81db70268;hpb=5687a16fc1b60345c76d4f5088edc41004a3529d;p=PuTTY.git

diff --git a/version.h b/version.h
index a9fab692..26242ad6 100644
--- a/version.h
+++ b/version.h
@@ -11,4 +11,25 @@
 #define TEXTVER "Unidentified build"
 #define SSHVER "PuTTY-Unidentified-Local-Build"
 #define BINARY_VERSION 0,0,0,0
+
+#ifndef SOURCE_COMMIT
+/*
+ * git commit id from which this build was made. This is defined by
+ * Buildscr for official builds - both source archives and prebuilt
+ * binaries - in the course of overwriting this file as described
+ * above. But we put it here under ifdef, so that it can also be
+ * passed in on the command line for Unix local development builds,
+ * which I treat specially because Unix developers - e.g. me - are
+ * quite likely to run 'make install' straight out of their dev
+ * directory so as to use the bleeding-edge code for day-to-day
+ * running.
+ *
+ * Windows doesn't really need the same treatment, because the easiest
+ * way to install a build properly on Windows is to run the installer,
+ * and the easiest way to do that is to run Buildscr, which will
+ * populate this field its own way. It's only the Unix automake build
+ * where you might go straight from local 'make' to 'make install'
+ * without going through Buildscr.
+ */
 #define SOURCE_COMMIT "unavailable"
+#endif