Differences

This shows you the differences between two versions of the page.

--- public:t-gede-13-1:lab1 [2013/01/15 10:53] – [Preparation] hannes
+++ public:t-gede-13-1:lab1 [2024/04/29 13:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 This lab is based on chapter 9 "The Ogre 3D Startup Sequence" from the book "Ogre 3D 1.7 - Beginner's Guide" by Felix Kerger, which will be given to you as a hand-out at the beginning of the lab class. But before you can start on the steps in the chapter, you will need to properly set up your development environment, this is covered below.
+===== Discussion =====
+Discussion thread for this lab (with updated notes) is here: [[http://ruclasses.proboards.com/index.cgi?board=gedespring2013&action=display&thread=111|Lab 1 Discussion Thread]]
 ===== Preparation =====
@@ Line 9: / Line 13: @@
   - Download and install [[http://www.ogre3d.org/download/sdk|OGRE 1.8.1 SDK for Visual C++ .Net 2010 (32-bit)]]. I recommend extracting this to a folder with a relatively short path and no spaces. E.g. into "C:\Development".
 To prepare your environment and project you need to:
-  - Create a system environment variable OGRE_HOME that points to Ogre SDK folder. You can then refer to this variable in your project setup as $(OGRE_HOME). This is so that you can easily take your project to a different machine where Ogre might be installed in a different folder. If each machine defines this variable, the project should be able to find the needed includes and libraries (see below).
+  - Create a system environment variable **OGRE_HOME** that points to Ogre SDK folder. You can then refer to this variable in your project setup as $(OGRE_HOME). This is so that you can easily take your project to a different machine where Ogre might be installed in a different folder. If each machine defines this variable, the project should be able to find the needed includes and libraries (see below).
-  - Add the SDK bin/debug and bin/release folders to your system "path" variable (for DLLs to be found)
+  - The Ogre run-time libraries (DLLs) are in folders called bin/debug and bin/release inside the SDK folder. You need to add these two folders to your system path variable so that the system can find them when you launch your application.
-  - Create a new project called "Lab1" inside a new solution called "GEDE2013" (it is a good idea to let VC++ create a folder for your solution - use the check box - and then your projects will appear inside that folder). The project should be a **WIN32 Console Application** and completely **empty**. You will write it from scratch.
+  - It is good to organize all your lab source code from the very beginning of this class to avoid a complete mess later. VC++ helps you organize the code into **solutions** and **projects**. A solution is really a collection of projects, which is a great way to keep track of labs. Once you launch VC++, create a new project called "Lab1" inside a new solution called "GEDE2013" (it is a good idea to let VC++ create a folder for your solution - use the check box - and then your projects will appear inside that folder). The project should be a **WIN32 Console Application** and completely **empty**. You will write it from scratch.
   - Right-click on your project inside VC++ and choose **properties**. Add Ogre folders and files in several locations within the properties:
     * C/C++->General->Additional Include Directories = ''$(OGRE_HOME)\include\OIS;$(OGRE_HOME)\include\OGRE;$(OGRE_HOME)\include;$(OGRE_HOME)\boost;%(AdditionalIncludeDirectories)''
@@ Line 19: / Line 23: @@
 ===== Lab Project =====
-Work through the enumerated actions in the hand-out given to you. What follows are some notes regarding those actions.
+Work through the enumerated actions in the hand-out given to you:
   - "Starting Ogre 3D"
@@ Line 33: / Line 37: @@
   - "Adding animation" (OPTIONAL)
+===== When You Are Finished =====
+Upload your **commented source files** into Lab1 in MySchool (zip them up if more than one). The lab projects will not be graded, but their completion counts towards your participation grade.