Renamed documentation files to .txt and converted them to DOS line endings so they would open properly on all systems.

Updated Makefile.in so "make dist" includes everything necessary for release.

--HG--
rename : BUGS => BUGS.txt
rename : COPYING => COPYING.txt
rename : CREDITS => CREDITS.txt
rename : INSTALL => INSTALL.txt
rename : README.android => README-android.txt
rename : README.cmake => README-cmake.txt
rename : README.DirectFB => README-directfb.txt
rename : README.gesture => README-gesture.txt
rename : README.HG => README-hg.txt
rename : README.iOS => README-ios.txt
rename : README.MacOSX => README-macosx.txt
rename : README.pandora => README-pandora.txt
rename : README.Platforms => README-platforms.txt
rename : README.Porting => README-porting.txt
rename : README.psp => README-psp.txt
rename : README.touch => README-touch.txt
rename : README.WinCE => README-wince.txt
rename : README => README.txt
rename : TODO => TODO.txt

INSTALL.txt

@@ -0,0 +1,27 @@
+
+To compile and install SDL:
+
+    0.  If you have downloaded this from the website, skip to the next step.
+        If you have checked this out from subversion, you'll need to run
+        ./autogen.sh to build the configure script. 
+
+    1.  Run './configure; make; make install'
+
+        If you are compiling for Windows using gcc, read the FAQ at:
+        http://www.libsdl.org/faq.php?action=listentries&category=4#42
+
+        If you are compiling using Visual C++ on Win32, you should read
+        the file VisualC.html
+
+    2.  Look at the example programs in ./test, and check out the online
+        documentation at http://wiki.libsdl.org/
+
+    3.  Join the SDL developer mailing list by sending E-mail to
+    	sdl-request@libsdl.org
+        and put "subscribe" in the subject of the message.
+
+        Or alternatively you can use the web interface:
+            http://www.libsdl.org/mailing-list.php
+
+That's it!
+Sam Lantinga <slouken@libsdl.org>