From Earlham Cluster Department

(Difference between revisions)
Jump to: navigation, search
(Directory Tree)
Line 44: Line 44:
=== Documentation ===
=== Documentation ===
* Entries from Background section above.
* Smoke Main Page - Outlines primary benefits of multi-threading in Games, and possibilities of use.
** Description of what's in each document, what it's useful for.
* Other papers Intel has published about Smoke.
* Fall IDF Presentation - Initial introduction of Smoke, outlines the challenges multi-core has presented to game development, and how Smoke solves those challenges.
** <i>Etc.</i>
* Gamefest Smoke Presentation - Explains how Smoke alleviates problems in Game Development, and how the Change Control Manager manages threads.
* GDC 08 Presentation - 7 zip files demonstrating games that have successfully used threading in games at the time, the Successes and Failures of each.
=== Directory Tree ===
=== Directory Tree ===
*bin - Contains Subdirectories which contain DLL files for both Release and Debug Versions, Also contains various .cdf, .odf, .gdf, .sdf files
*bin - Contains Subdirectories which contain DLL files for both Release and Debug Versions, Also contains various .cdf, .odf, .gdf, .sdf files

Revision as of 18:20, 16 February 2010


Porting Intel's Smoke Game Demo to Linux

N.B. - If you edit by section (using the "edit" links next to the section heading) you will be much less likely to cause a Save conflict.

Background Information

Near Term Tasks

  1. Examine all of the documentation and build an annotated index of it in the wiki. Materials that are on-line already, e.g. the ones listed above, can have URLs and annotations. Ones that come with the source kit should just have titles, file system paths, and annotations. We don't want to upload those to the wiki without first checking with Intel about re-publishing their materials. (Nick)(Done!)
  2. Examine all of the source kit's directory tree and build an annotated map of it in the wiki. (Nick)(Currently Working On)
  3. Examine all of the #includes in Smoke.cpp and propose solutions for porting/converting/removing each of them. Remember that #includes nest, we need to follow each thread starting with the ones in Smoke.cpp. (Sam)(Done!)
  4. Figure-out roughly how each of these works, what the dependencies are, etc. and propose a solution for porting/converting/removing each of them:
    • Logging (Gil)
    • Debugging (Gil)
    • EngineExecuteGDF (Gil)
    • main() in Smoke.cpp (Gil)
    • Argument processing in Smoke.cpp (Gil)
  5. Develop an ordered plan in the wiki (collective, in class on Tuesday)
    • Modules
    • Libraries
      • Ogre/OpenGL replacing DirectX (Sam)
      • Find and guard/eliminate .NET stuff (To Do)
      • DirectX -> ? conversion for SystemInput and SystemFire (To Do)
      • Havoc (Future)
    • Functionality
  6. Figure-out Doxygen and build a doc set (Sam)(Done!)
  7. Figure-out Make and construct the first simple Makefile that builds Smoke (collective, in class on Tuesday)


Directory Tree

Note: Ogre subdirectories already include many things pertaining to Linux and OpenGL, so rendering differently may be easier than expected.

Smoke.cpp #include Files

System Path #include files

Format is: (A file that includes the header) #include <(include file)>





Ogre/OpenGL replacing Ogre/DirectX

High-level 3D graphics engine

OpenGL, DirectX, or Cg

Figure out how DirectX is being used and switch out DirectX functionality (HLSL in Ogre), with OpenGL (GLSL).

 ? replacing .NET

DirectX -> ? conversion for SystemInput and SystemFire

Personal tools
this semester