Differences

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

--- public:t-gede-16-1:lab1 [2016/01/10 09:49] – [Preparation] marino
+++ public:t-gede-16-1:lab1 [2024/04/29 13:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 This first Lab assignment is intended to get the Ogre3D environment started. Getting the development environment set up and configured can be a little tricky for the first time, so this Lab will be solely used to get the "Hello World" of Ogre3D built.\\
-There will be a pdf guide that will take you through the basic application step by step. I strongly encourage you to try to understand the steps not just writing it down like a zombie parrot, as the follow up Labs will all be built on top of the base you create in Lab 1.
+There will be a pdf guide that will take you through the basic application step by step. I strongly encourage you to try to understand the steps not just writing it down like a parrot, as the follow up Labs will all be built on top of the base you create in Lab 1.
 ===== Discussion =====
-Discussion thread for this lab will be on Piazza: [[https://piazza.com/class/hq7dlipqggr2qe?cid=6|Lab 1 Discussion Thread]]. Please don't hesitate to ask questions or comment on the Lab assignment.
+Discussion thread for this lab will be on Piazza: [[https://piazza.com/class/ij2xbg3ztb41qt|Lab 1 Discussion Thread]]. Please don't hesitate to ask questions or comment on the Lab assignment.
 ===== Preparation =====
+  - Download and install C++ development environment, the instructions will assume you are using the [[https://www.microsoft.com/en-us/download/details.aspx?id=34673|MS Visual C++ Express 2012 environment]], which you can get for free. You're free to use other environments or platforms as long as you take care of making it work on your own (with the help of the Internet).\\ \\
-- Download and install C++ development environment, the instructions will assume you are using the [[http://www.microsoft.com/visualstudio/eng/downloads#d-2010-express|MS Visual C++ Express 2010 environment]], which you can get for free. You're free to use other environments or platforms as long as you take care of making it work on your own (with the help of the Internet).
+  - Download and install [[http://www.ogre3d.org/download/sdk|OGRE 1.9 SDK for Visual C++ 2012 (32-bit)]]. I recommend extracting this to a folder with a relatively short path and **no spaces**. E.g. into "C:\OgreSDK". You are free to use other versions, but be advised you will be rowing your own boat if problems arise :)
-  - Download and install [[http://www.ogre3d.org/download/sdk|OGRE 1.9 SDK for Visual C++ 2010 (32-bit)]]. I recommend extracting this to a folder with a relatively short path and no spaces. E.g. into "C:\OgreSDK". You are free to use other versions, but be advised you will be rowing your own boat if problems arise :)
@@ Line 17: / Line 16: @@
-  - **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). ''example: C:\Ogre1.9_vc100\OgreSDK_vc10_v1-9-0''
+  - **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). ''example: C:\Ogre1.9_vc100\OgreSDK_vc10_v1-9-0''\\ \\
-  - **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 keep track of labs. Once you launch VC++, create a new project called "Lab1" inside a new solution called "GEDE2015" (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 "GEDE2015" (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++ project explorer** and choose ''properties''. Add Ogre folders and files in several locations within the properties:<box red 100% | Note: >We will be changing configurations for debug builds as well as release builds. So take note that the strings are not always the same for both builds.
 </box>
-  - **Change your build output directory:** Configuration Properties->General->Output Directory\\ Add ''$(ProjectName)\'' at the end of the output directory so it will look like:''$(SolutionDir)$(Configuration)\$(ProjectName)\''\\ This will help with organizing the builds for each lab project.{{ :public:t-gede-14-1:gede_lab1_outputdir.png?nolink |}}
+  - **Change your build output directory:** Configuration Properties->General->Output Directory\\ Add ''$(ProjectName)\'' at the end of the output directory so it will look like:''$(SolutionDir)$(Configuration)\$(ProjectName)\''\\ This will help with organizing the builds for each lab project.{{ :public:t-gede-14-1:gede_lab1_outputdir.png?nolink |}}\\ \\
   - **Add additional include libraries:** C/C++->General->Additional Include Directories = **Notice, for all configurations!**<code>$(OGRE_HOME)\include\OIS;$(OGRE_HOME)\include\OGRE;$(OGRE_HOME)\include;$(OGRE_HOME)\boost;%(AdditionalIncludeDirectories)</code> <box red 100% | Note: >If the C/C++ tab is missing. For some reason, with some versions of Visual Studio you will need to have created a cpp file in order to get the C/C++ tab in the configuration properties, so adding a main.cpp file with a basic "hello world" to the project and building it will suffice. )
-</box>{{ :public:t-gede-14-1:gede_lab1_additional_include_directories.png?nolink |}}
+</box>{{ :public:t-gede-14-1:gede_lab1_additional_include_directories.png?nolink |}}\\ \\
   - **Add connections to additional Ogre and input libraries:** Linker->Input->Additional Dependencies  <code>Debug:   OgreMain_d.lib;OIS_d.lib;%(AdditionalDependencies)
 Release: OgreMain.lib;OIS.lib;%(AdditionalDependencies)
 </code> <box red 100% | Note:>Add this to the end of the current string, do not replace it, and make sure to seperate it with a semicolon.</box>{{ :public:t-gede-14-1:gede_lab1_additionaldepend_debug.png?nolink |}}{{ :public:t-gede-14-1:gede_lab1_additionaldepend_release.png?nolink |}}
   - **Also you will need to add additional Library folders** where the Ogre specific libraries and the required boost libraries are stored: Linker->General->Additional Library Directories =<code>Debug: $(OGRE_HOME)\boost\lib;$(OGRE_HOME)\lib\debug;%(AdditionalLibraryDirectories)
-Release: $(OGRE_HOME)\boost\lib;$(OGRE_HOME)\lib\Release;%(AdditionalLibraryDirectories)</code>{{ :public:t-gede-14-1:gede_lab1_debug_additional_libs.png?nolink |}}{{ :public:t-gede-14-1:gede_lab1_release_additional_libs.png?nolink |}}
+Release: $(OGRE_HOME)\boost\lib;$(OGRE_HOME)\lib\Release;%(AdditionalLibraryDirectories)</code>{{ :public:t-gede-14-1:gede_lab1_debug_additional_libs.png?nolink |}}{{ :public:t-gede-14-1:gede_lab1_release_additional_libs.png?nolink |}}\\ \\
   - **If you are using a different version of Visual studio than 2012,** make sure to be using the vc110 toolset <code>Project Configuration->General->Platform Toolset = Visual Studio 2012 (v110)
-</code> <box red 100% | Note: >If the v110 toolset is not available, you will need to install VS 2012 express, whether you use it or not, or at least the correct VC++ toolset (let me know if you find out how ;)</box>{{ :public:t-gede-16-1:ogre3d-select-buildtoolsv110.png?nolink |}}
+</code> <box red 100% | Note: >If the v110 toolset is not available, you will need to install VS 2012 express, whether you use it or not, or at least the correct VC++ toolset (let me know if you find out how ;)</box>{{ :public:t-gede-16-1:ogre3d-select-buildtoolsv110.png?nolink |}}\\ \\
   - **Set up the engine configuration files.**
     - Now navigate to your solution folder ''In my case: C:\Code\GEDE2015_Ogre_Labs'' and create a new Folder called ''LabFiles'',