Correctly handle the version string, defined in a single place now.

Fix and update README.

Makefile

@@ -4,12 +4,11 @@
 # Don't print directory as we descend into them
 MAKEFLAGS += --no-print-directory
 
-# The project version
-export PROJECTVERSION=0.0.2-svn
-
-# This should eventually be computed if compiling out-of-tree is implemented
 export CT_TOP_DIR=$(shell pwd)
 
+# This is crosstool-ng version string
+export CT_VERSION=$(shell cat $(CT_TOP_DIR)/version)
+
 .PHONY: all
 all: build
 

README

@@ -1,9 +1,9 @@
 This is the README for crosstool-NG
 
-To get you started, hust enter:
+To get you started, just enter:
   make help
 
 You can find a (terse and WIP) documentation in docs/.
 
 You can also point your browser to
-  http://ymorin.is-a-geek.org/dokuwiki/doku.php?id=projects:crosstool
+  http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool

kconfig/Makefile

@@ -16,6 +16,9 @@ ifneq ($(KBUILD_NO_NLS),)
 CFLAGS += -DKBUILD_NO_NLS
 endif
 
+# Derive the project version from, well, the project version:
+export PROJECTVERSION=$(CT_VERSION)
+
 menuconfig: $(obj)/mconf
 	@$< $(KCONFIG_TOP)
 

scripts/crosstool.sh

@@ -182,7 +182,7 @@ CT_SYS_PROCESSOR=`uname -p`
 CT_SYS_USER="`id -un`"
 CT_SYS_DATE=`CT_DoDate +%Y%m%d.%H%M%S`
 CT_SYS_GCC=`gcc -dumpversion`
-CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_SYS_DATE} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME} for ${CT_TARGET}"
+CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_SYS_DATE} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
 
 # Redirect log to the actual log file now we can
 # It's quite understandable that the log file will be installed in the install

scripts/functions

@@ -20,9 +20,6 @@ trap CT_OnError ERR
 set -E
 set -o pipefail
 
-# This is crosstool-ng-0.0.1
-CT_VERSION=ng-0.0.1
-
 # The different log levels:
 CT_LOG_LEVEL_ERROR=0
 CT_LOG_LEVEL_WARN=1

version

@@ -0,0 +1 @@
+0.0.2-svn