Building Horde3D - Revision history

Zuck at 12:29, 13 February 2014

2014-02-13T12:29:30Z

2013-10-14T13:19:14Z

2013-10-14T13:17:08Z

2010-09-18T15:37:25Z

2010-05-18T01:05:36Z

Added command line build instructions for Mac OS X

2010-03-25T11:52:14Z

2010-02-09T06:26:31Z

2010-02-09T06:23:41Z

Linkage order on Linux

2010-01-03T17:43:05Z

2010-01-03T16:44:39Z

← Older revision		Revision as of 12:29, 13 February 2014
Line 1:		Line 1:
−	~~__NOTOC__ __NOEDITSECTION__~~{{ContentBlock\|color=~~white~~\|content=~~{{!~~!}}	+	{{ContentBlock \| width=100% \| thickness=1 \| color=#ff0000 \| content-color=#ffcccc \| content=
		+	'''This page is out-of-date! Don't trust it...'''
		+	}}
		+
	This article contains instructions for building Horde3D from source on all supported platforms. Since Horde3D is very lightweight and has a minimal amount of external dependencies, getting it to compile and run is usually quite straightforward.		This article contains instructions for building Horde3D from source on all supported platforms. Since Horde3D is very lightweight and has a minimal amount of external dependencies, getting it to compile and run is usually quite straightforward.

@@ Line 28: / Line 28: @@
 '''WRONG''':
-   gcc -o app main.cpp -lGL '''-lHorde3D'''
+   g++ -o app main.cpp -lGL '''-lHorde3D'''
 '''RIGHT''':
-   gcc -o app main.cpp '''-lHorde3D''' -lGL
+   g++ -o app main.cpp '''-lHorde3D''' -lGL
 This is required for GCC 3.x and 4.x series on Linux. If you don't follow the linkage order, you will get [http://horde3d.org/forums/viewtopic.php?f=2&t=384 glCreateShader error within h3dInit call].

@@ Line 61: / Line 61: @@
 }}
 ==== A minimal app to test your include\linker settings ====
-   #include"glfw.h"
+   #include "glfw.h"
-   #include"Horde3D.h"
+   #include "Horde3D.h"
-   #include"Horde3DUtils.h"
+   #include "Horde3DUtils.h"
    int main()
+   {

← Older revision		Revision as of 15:37, 18 September 2010
Line 60:		Line 60:

	}}		}}
		+	==== A minimal app to test your include\linker settings ====
		+	#include"glfw.h"
		+	#include"Horde3D.h"
		+	#include"Horde3DUtils.h"
		+	int main()
		+	{
		+	glfwInit();
		+	if(!glfwOpenWindow(640,480,8,8,8,8,24,8,GLFW_WINDOW))
		+	{
		+	glfwTerminate();
		+	return 1;
		+	}
		+	h3dInit();
		+	h3dRelease();
		+	glfwCloseWindow();
		+	glfwTerminate();
		+	}

@@ Line 49: / Line 49: @@
 ==== The Unix Way Using the Command Line ====
-''TODO''
+To create the Makefiles, you have to install CMake first. After installing the CMake command line tools (so choose NOT to skip the installation when asked during the CMake installation), you should be able to run CMake from the console. Switch to Horde3D root directory and create a new directory in which the CMake output will be stored, for example ''CMake''. Change the current directory to that newly created one and type
 }}

@@ Line 41: / Line 41: @@
 ==== The Mac Way Using Xcode ====
-To create the Xcode project files, you have to install CMake first. After installing the CMake command line tools, you should be able to run CMake from the console. Switch to Horde3D root directory and create a new directory in which the CMake output will be stored, for example ''CMake''. Change the current directory to that newly created one and type
+To create the Xcode project files, you have to install CMake first. After installing the CMake command line tools (so choose NOT to skip the installation when asked during the CMake installation), you should be able to run CMake from the console. Switch to Horde3D root directory and create a new directory in which the CMake output will be stored, for example ''CMake''. Change the current directory to that newly created one and type
    cmake -G "Xcode" ..

@@ Line 25: / Line 25: @@
 === Linkage order for your application ===
-You must link Horde3D library to your final executable before GL one:
+You must link Horde3D library to your final executable before GL one.
 '''WRONG''':

← Older revision		Revision as of 06:23, 9 February 2010
Line 23:		Line 23:

	which will create the makefiles. Once they are created, you can type <tt>make</tt> to build the code or <tt>make clean</tt> to remove all generated files.		which will create the makefiles. Once they are created, you can type <tt>make</tt> to build the code or <tt>make clean</tt> to remove all generated files.
		+
		+	=== Linkage order for your application ===
		+	You must link Horde3D library to your final executable before GL one:
		+
		+	'''WRONG''':
		+	gcc -o app main.cpp -lGL '''-lHorde3D'''
		+
		+	'''RIGHT''':
		+	gcc -o app main.cpp '''-lHorde3D''' -lGL
		+
		+	This is required for GCC 3.x and 4.x series on Linux. If you don't follow the linkage order, you will get [http://horde3d.org/forums/viewtopic.php?f=2&t=384 glCreateShader error within h3dInit call].

	== Building on Max OS X ==		== Building on Max OS X ==

@@ Line 4: / Line 4: @@
 == Obtaining the SDK ==
-Besides the [http://sourceforge.net/projects/horde3d/files/ official releases], there is also a [http://sourceforge.net/svn/?group_id=215373 subversion repository hosted at SourceForge] which is usually more up-to-date than the stable point releases.
+Besides the [http://sourceforge.net/projects/horde3d/files/ official release packages], there is also a subversion repository hosted at SourceForge which is usually more up-to-date than the stable point releases.
 The repository has the common SVN structure ''branches'', ''tags'' and ''trunk''. The latest development snapshot can be found in the ''trunk'' folder, while the official releases are tagged in the ''tags'' folder. If you check out the trunk folder, you will get the SDK along with all official extensions.
-The following command can be used to check out the latest WIP version of Horde3D:
+See [[SVN Source Instructions]] for instructions on how to obtain code from Subversion.
 == Building on Windows ==

@@ Line 1: / Line 1: @@
-__NOTOC__
+__NOTOC__ __NOEDITSECTION__{{ContentBlock|color=white|content={{!!}}
 This article contains instructions for building Horde3D from source on all supported platforms. Since Horde3D is very lightweight and has a minimal amount of external dependencies, getting it to compile and run is usually quite straightforward.
@@ Line 42: / Line 41: @@
 ''TODO''