* Master/source-distribution.make (svn-tag): Add comment line

(svn-dist): Simplify checkout.
* Master/framework.make: Add build-headers rules
* GNUmakefile: Add special_prefix to GNUSTEP_MAKEFILES


git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@22719 72102866-910b-0410-8b05-ffd578937521

ChangeLog

@@ -1,3 +1,10 @@
+2006-03-27  Adam Fedor  <fedor@gnu.org>
+
+	* Master/source-distribution.make (svn-tag): Add comment line
+	(svn-dist): Simplify checkout.
+	* Master/framework.make: Add build-headers rules
+	* GNUmakefile: Add special_prefix to GNUSTEP_MAKEFILES
+
 2006-03-17  Richard Frith-Macdonald <rfm@gnu.org>
 
 	* Documentation/README.MinGW: Attempt to clarify versions to be used.

Documentation/README.MinGW

@@ -107,11 +107,9 @@ From this window we can now start building things.
 The main GNUstep project pages tell you how to get hold of this. You can get
 the latest release of the following libraries. However, since MinGW support
 is currently evolving, we recommend that you get the latest snapshot
-or code from CVS.
-
-export CVS_RSH=ssh
-cvs -z3 -d:ext:anoncvs@savannah.gnu.org:/cvsroot/gnustep co core
+or code from SVN.
 
+svn co http://svn.gna.org/svn/gnustep/modules/core
 
 6. Installing gnustep-make
 ==========================

Documentation/faq.texi

@@ -363,9 +363,9 @@ good idea to get in touch with Adam or Richard to coordinate efforts.
  You can write testcases - where the libraries fail tests, you
 could either fix the problem, or add it to the task list.
 
-To write testcases, you need to use anonymous CVS to install the latest
-GNUstep snapshots you can find. Then checkout the
-'gnustep/dev-apps/test/Testsuite' module from CVS.
+To write testcases, you need to use svn to install the latest
+GNUstep sourcecode you can find. Then checkout the
+'gnustep/tools/testsuite' module from svn.
 
 @node How do I start writing applications?, How can I help with the GNUstep website?, How do I start writing tests?, Compiling and Developing
 @subsection  How do I start writing applications?
@@ -385,7 +385,7 @@ generated from files in the individual GNUstep packages.
 
 If you want to update the FAQ or documentation  - grab
 the latest snapshot of the GNUstep core you can find, update it
-from the CVS repository, and work with the contents of the appropriate
+from the svn repository, and work with the contents of the appropriate
 documentation directory.
 
 If you want to work on other parts of the website, you can grab a copy

Documentation/gnustep-howto.texi

@@ -58,7 +58,7 @@ any later version published by the Free Software Foundation.
 * Additional Installation::     
 * Tools and Applications::      
 * Machine Specific::            
-* Anonymous CVS::               
+* Source via SVN::               
 @end menu
 
 @node Introduction, Preliminaries, Top, Top
@@ -417,13 +417,13 @@ Good Luck!
 @include machines.texi
 
 
-@node Anonymous CVS,  , Machine Specific, Top
-@chapter Getting Libraries via Anonymous CVS
+@node Source via SVN,  , Machine Specific, Top
+@chapter Getting Libraries via SVN
 
 If you didn't get one of the snapshots, or if you want to be sure to
-stay on the bleading edge, then you should get the libraries via CVS. Go
-to @url{http://savannah.gnu.org/cvs/?group_id=99} for information on how
-to get anonymous CVS access.
+stay on the bleading edge, then you should get the libraries via SVN. Go
+to @url{http://www.gnustep.org/resources/sources.html} for information on how
+to get the sourcecode.
 
 If you haven't already done so, change to the directory, where you
 want the source to reside. To get a list of potential modules to check out,

GNUmakefile.in

@@ -38,6 +38,7 @@ GNUSTEP_CONFIG_FILE_DIR = $(dir $(GNUSTEP_CONFIG_FILE))
 GNUSTEP_SYSTEM_ROOT = $(special_prefix)@GNUSTEP_SYSTEM_ROOT@
 GNUSTEP_LOCAL_ROOT  = $(special_prefix)@GNUSTEP_LOCAL_ROOT@
 GNUSTEP_NETWORK_ROOT = $(special_prefix)@GNUSTEP_NETWORK_ROOT@
+makedir = $(special_prefix)@GNUSTEP_MAKEFILES@
 srcdir = @srcdir@
 VPATH = @srcdir@
 
@@ -62,7 +63,6 @@ export GNUSTEP_TARGET_DIR
 export GNUSTEP_TARGET_LDIR
 export MAYBE_LIBRARY_COMBO
 
-makedir = @GNUSTEP_MAKEFILES@
 tooldir = $(GNUSTEP_SYSTEM_ROOT)/Tools
 
 INSTALL		= @INSTALL@

Master/framework.make

@@ -26,9 +26,15 @@ endif
 
 FRAMEWORK_NAME := $(strip $(FRAMEWORK_NAME))
 
-# A framework has a special task to do before-all, which is to build 
+before-build-headers::
+
+after-build-headers::
+
+# A framework has a special task to do before all, which is to build 
 # the public framework headers.
-before-all:: $(FRAMEWORK_NAME:=.build-headers.framework.variables)
+build-headers:: before-build-headers $(FRAMEWORK_NAME:=.build-headers.framework.variables) after-build-headers
+
+before-all:: build-headers
 
 internal-all:: $(FRAMEWORK_NAME:=.all.framework.variables)
 $(FRAMEWORK_NAME:=.all.framework.variables): $(FRAMEWORK_NAME:=.build-headers.framework.variables)

Master/source-distribution.make

@@ -197,7 +197,7 @@ endif
 # Tag the SVN source with the $(SVN_TAG_NAME)-$(VERTAG) tag
 #
 svn-tag:
-	$(SVN) copy $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/trunk $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/tags/$(SVN_TAG_NAME)-$(VERTAG)
+	$(SVN) copy $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/trunk $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/tags/$(SVN_TAG_NAME)-$(VERTAG) -m "Tag version $(VERTAG)"
 
 #
 # Build a .tar.gz from the SVN sources using revision/tag 
@@ -218,9 +218,8 @@ internal-svn-export:
 	  echo "*Error* cannot export: $(SVN_MODULE_NAME) already exists"; \
 	  exit 1; \
 	fi; \
-	$(SVN) export $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/$(EXPORT_SVN_NAME) $(SVN_MODULE_NAME); \
+	$(SVN) export $(SVN_BASE_URL)/$(SVN_MODULE_NAME)/$(EXPORT_SVN_NAME) $(VERSION_NAME); \
 	echo "Generating $(ARCHIVE_FILE)"; \
-	mv $(SVN_MODULE_NAME) $(VERSION_NAME); \
 	if [ -f $(ARCHIVE_FILE) ]; then            \
 	  echo "$(ARCHIVE_FILE) already exists:";   \
 	  echo "Saving old version in $(ARCHIVE_FILE)~"; \