public:t-gede-13-1:lab1
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
public:t-gede-13-1:lab1 [2013/01/15 11:07] – [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" | This lab is based on chapter 9 "The Ogre 3D Startup Sequence" | ||
+ | |||
+ | ===== Discussion ===== | ||
+ | |||
+ | Discussion thread for this lab (with updated notes) is here: [[http:// | ||
===== Preparation ===== | ===== Preparation ===== | ||
Line 11: | Line 15: | ||
- 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). | ||
- 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. | - 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. | ||
- | - 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 think of these lab classes. Once you launch VC++, create a new project called " | + | - 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 " |
- Right-click on your project inside VC++ and choose **properties**. Add Ogre folders and files in several locations within the properties: | - Right-click on your project inside VC++ and choose **properties**. Add Ogre folders and files in several locations within the properties: | ||
* C/ | * C/ | ||
Line 19: | Line 23: | ||
===== Lab Project ===== | ===== 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: |
- " | - " | ||
Line 33: | Line 37: | ||
- " | - " | ||
+ | ===== 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. |
/var/www/cadia.ru.is/wiki/data/attic/public/t-gede-13-1/lab1.1358248032.txt.gz · Last modified: 2024/04/29 13:32 (external edit)