Import irrlicht 1.8.4 release

bin/Linux/readme.txt

@@ -0,0 +1,4 @@
+If you wish to compile the engine in linux yourself, 
+goto the \source directory. Run a 'make' in the subfolder 'Irrlicht'.
+After this, you should be able to make all example applications in \examples.
+Then just start an X Server and run them, from the directory where they are.

bin/MacOSX/readme.txt

@@ -0,0 +1,5 @@
+The Irrlicht Engine is staticly compiled together with the application under MacOSX. 
+
+If you wish to compile the engine in MacOSX yourself, use the source in the \source directory.
+
+Please note that this SDK has not been tested on MacOSX. Get a SDK especially for MacOSX on http://irrlicht.sf.net

bin/Win32-VisualStudio/readme.txt

@@ -0,0 +1,25 @@
+The Win32-VisualStudio version is currently (Irrlicht 1.8) compiled with VS 2010 using the Windows 7.1 SDK as platform toolset.
+You might get the necessary Windows Platform SDK here: http://msdn.microsoft.com/en-us/windows/bb980924.aspx
+
+To link to that Irrlicht.dll you need to set platform toolset in your VS version to the same target or re-compile the Irrlicht.dll using another platform toolset.
+
+To re-compile Irrlicht for Win32-VisualStudio:
+There are several project files for different VS versions in source/Irrlicht.
+Irrlicht10.0.sln is for VS 2010
+Irrlicht11.0.sln is for VS 2012
+Irrlicht12.0.sln is for VS 2013
+
+To compile Irrlicht + all examples and all tools check the BuildAllExamples_*.sln files in the examples folder.
+
+For newer VS versions you have update one of those projects (VS usually can do that automatically when you open an older solution file).
+
+Currently each of those solutions does set the platform toolset "Windows 7.1 SDK" (to be compatible to each other). 
+You might want to change that in the project settings and set it to your current version.
+Make sure you use the same platform toolset in your application and in the engine.
+Also when compiling examples each example has to use the same platform toolset as was used for the engine.
+
+Platform should be Win32
+Configuration is by default "Release"
+But you can also chose "Debug" if you want Irrlicht with Debug information.
+Static builds are possible but you have to additionally set the _IRR_STATIC_LIB_ define in the application when linking to a static Irrlicht.lib
+

bin/Win32-gcc/readme.txt

@@ -0,0 +1,16 @@
+If you wish to compile Irrlicht for Win32-gcc you have several choices.
+
+1. You can work from within a MinGW shell.
+Go to the folder source/Irrlicht and run the Makefile with:
+make win32 
+Examples can be build by going into the folder of the example (for example examples/01.HelloWorld) and running the Makefile with:
+make all_win32
+
+2. Use the Code::Blocks IDE
+There is a project file called Irrlicht-gcc.cbp in source/Irrlicht to compile just the engine.
+Be sure to select a Windows target like "Win32 - release - accurate math - dll"
+
+There is also Code::Blocks workspace file in the examples folder called BuildAllExamples.workspace
+Again be sure to select a Windows target like "Win32 - release - accurate math - dll"
+This workspace allows you to compile the engine together with all examples and tools.
+

bin/Win64-VisualStudio/readme.txt

@@ -0,0 +1,24 @@
+The Win64-VisualStudio version is currently (Irrlicht 1.8) compiled with VS 2010 using the Windows 7.1 SDK as platform toolset.
+You might get the necessary Windows Platform SDK here: http://msdn.microsoft.com/en-us/windows/bb980924.aspx
+
+To link to that Irrlicht.dll you need to set platform toolset in your VS version to the same target or re-compile the Irrlicht.dll using another platform toolset.
+
+To re-compile Irrlicht for Win32-VisualStudio:
+There are several project files for different VS versions in source/Irrlicht.
+Irrlicht10.0.sln is for VS 2010
+Irrlicht11.0.sln is for VS 2012
+Irrlicht12.0.sln is for VS 2013
+
+To compile Irrlicht + all examples and all tools check the BuildAllExamples_*.sln files in the examples folder.
+
+For newer VS versions you have update one of those projects (VS usually can do that automatically when you open an older solution file).
+
+Currently each of those solutions does set the platform toolset "Windows 7.1 SDK" (to be compatible to each other). 
+You might want to change that in the project settings and set it to your current version.
+Make sure you use the same platform toolset in your application and in the engine.
+Also when compiling examples each example has to use the same platform toolset as was used for the engine.
+
+Platform should be Win64
+Configuration is by default "Release"
+But you can also chose "Debug" if you want Irrlicht with Debug information.
+Static builds are possible but you have to additionally set the _IRR_STATIC_LIB_ define in the application when linking to a static Irrlicht.lib