build.txt

/**
\page OOLuaBuilding Building
\brief

	OOLua's source code can either be dropped into the path for a project
	, \ref OOLuaAmalagate "amalgamated" to a single header and source file or compiled as a
	static library.\n

	\section OOLuaPremake Makefiles and IDE projects
	OOLua does not provide solution files instead it provides Premake4
	\ref PremakeDownload "[1]" scripts. Premake is a simple
	\ref PremakeQuickStart "[2]" to use IDE project or makefile generator
	that can be used to help create a static library or to run
	\ref OOLuaUnitTests \n
		\subsection OOLuaPremakeFormat Premake format
		premake4 [make or IDE] [target operating system]
			\subsubsection OOLuaPremakeMakefile Makefile
			\code premake4 gmake [] \endcode
			\li macosx
			\li linux
			\subsubsection OOLuaPremakeXcode Xcode
			\code premake4 xcode[] macosx \endcode
			\li 3
			\li 4
			\note macosx is required
			\subsubsection OOLuaPremakeVisualStudio Visual Studio
			\code premake4 vs[] windows \endcode
			\li 2005
			\li 2008
			\li 2010
			\li 2013
			\note windows is required
			\subsubsection OOLuaPremakeCodeBlocks CodeBlocks
			\code premake4 codeblocks [] \endcode
			\li windows
			\li linux
			\li macosx

	\section IncreasingLibraryLimits Library limits
	\copydetails OOLuaFileGeneration

	\section LibraryConfig Library Config
		\see OOLuaConfig

	\section OOLuaBuildScripts Build Scripts
	\code [make or IDE]_build.[sh or bat]\endcode
	When these build scripts are run from the build_scripts directory
	they create a "../local_install" directory into which newly compiled
	debug and release static libraries will be place along with the
	library headers in a sub directory "oolua".\n

	\section OOLuaTestScripts Test Unit scripts
	\details
	\code [make or IDE]_tests.[sh or bat]\endcode
	The scripts test the library \ref OOLUA_USE_EXCEPTIONS "using exceptions"
	and \ref OOLUA_STORE_LAST_ERROR "error return values" in both debug and
	release configurations. When run from the build_scripts directory these
	will produce compiler and test unit output saved to disk in the
	directory "../build_logs", if an error occurs during a test then a
	message to stdout will inform of where to locate the full error message
	and compile log. These test scripts clean up any other files produced
	during their running.

	\anchor PremakeDownload
	[1] Premake download http://industriousone.com/premake/download
	<p>
	\anchor PremakeQuickStart
	[2] Premake quick start http://industriousone.com/premake-quick-start
	<p>
*/