OS X Ogre Eihort SDK

It’s been a while since I have posted any news, but the time has finally come. I have put together a SDK installer for Ogre Eihort on OS X.

Included in the SDK…

Ogre Framework
Ogre Command Line Tools
Xcode Project Templates
Additional Frameworks (CEGUI, CG)
OIS Library
Demo Applications and Media

I encourage all OS X users of Ogre to check out the SDK and provide feedback on the package. I am thinking I still need to add in the Example Application framework files, the source code to the demos, and a few more Xcode Templates. Until then the source release is also available, so don’t hesitate to grab it if you find something missing.

Ogre Eihort Universal OS X SDK - 33.1 MB
*Note: The latest SDK as well as the Command Line Tools and Xcode Project Templates are available on the Ogre website under the Download section.

About this entry

You’re currently reading “OS X Ogre Eihort SDK,” an entry on Tricky Fly Blog

Published:: 03.29.07 / 5pm

Category:: Ogre, Mac OS X

Bookmark:: del.icio.us digg Y!

About

My name is Justin Walsh. I am a recent graduate of the University of Advancing Technology, and majored in Software Engineering.

I am currently working with MegaDotNet on several software projects. These projects range from web applications using Ruby on Rails, to 3D Graphics Simulations developed in C++.

In my spare time I also work on Ogre3D, an open source graphics engine. I am currently the Macintosh Maintainer and my contributions include universal binary support, bundle-able frameworks for OS X, the Mac SDK, and integrating Cocoa and Carbon platform support into the Macintosh port of Ogre.

Feel free to contact me if you have questions, suggestions, or just want to say hello.

brian 04.01.07 / 4pm

cool! however, my Ogre Cocoa Application XCode project template folder is empty… how come? only Carbon support for now?

/Library/Application Support/Apple/Developer Tools/Project Templates/Ogre/Ogre Cocoa Application

Justin Walsh 04.01.07 / 4pm

Brian,

Yep, I plan on including another template for Cocoa Applications, as well as Example Application based Applications in the not so distant future.

monsterkodi 04.07.07 / 8am

seems to work fine. most of the demos are running smoothly.

is the source code of the OIS port available?
and is it possible that the joystick handling doesn’t work?

yours kodi

Asier 04.10.07 / 7am

Oh! That Cocoa App would be nice. Is any way to extend the app menu’s and include key accelerators? I’m having problems exiting the active applicaion.

Justin Walsh 04.10.07 / 3pm

Kodi,

I am in the middle of wrapping up the OIS source and will be committing it to the OIS SVN repository, school work is currently taking up most of my time so expect that update in the not so distant future. Also, there is still no joystick support in OIS for OS X.

Asier,

You must seek out the documentation of the API you are using, there are plenty of ways to work with application menus and such in both Carbon and Cocoa. I would personally start with Interface Builder, as Ogre is built to support being embedded in your own windows if you choose.

Chad Hill 06.05.07 / 4pm

Justin,

Great stuff with this SDK. I immediately downloaded it and set about migrating our current ogre project from Visual Studios to XCode. First time I’ve done it, but using the frameworks provided and good bit of refactoring lazy MS style C++, we’ve made cross platform a reality for us.

And yes, ExampleApplication.h, etc would be nice in the SDK.

ryan 11.03.07 / 11pm

The template “cannot be parsed” in Leopard/XCode

Justin Walsh 11.06.07 / 12am

ryan,

I haven’t tried the Xcode project templates in Xcode 3 yet, so thanks for the heads up.

Ryan 11.24.07 / 3am

I’ve got the templates installed… They still work to some extent.

However, it looks in Library/Frameworks for Ogre.Framework. I just pointed it to the build location.

It also can’t find the header files… Do I need to change another path somewhere?

Ryan 11.25.07 / 3pm

You need to manually include the path to the Framework in your Frameworks search path… UNLESS you put the Framework in /Library/Frameworks…

Which may be a better solution for developers afterall. It still allows you to package the framework into the app properly.

Sorry, it may not have been clear… If you simply copy Ogre.Framework to /Library/Frameworks, the template still works as is.

On a slight tangent, can frameworks be linked per configuration? i.e. Can the Debug configuration link to the Debug Ogre.Framework and Release to Release? That otherwise you would have to be sure to update the framework to release when you’re ready to ship.

Cheers

Justin Walsh 11.25.07 / 3pm

Ryan,

The newer Ogre Mac SDK does not force you to place your Ogre.framework or the SDK files in any specific directory like the previous packaged SDK, the newest SDK does not use an installer package. This means that there is no (easy) way to really build a Project Template that will know where your SDK files and Ogre.Framework have been placed.

So, like you discovered changing the header and framework search paths will fix the template. My advise would be to delete the Ogre.Framework reference after the template is loaded up, then drag in your Ogre.framework, this should update the framework search paths for you.

If you are wanting to access your headers in the non framework style… i.e. Ogre.h vs Ogre/Ogre.h you must update the header search path to the location of your Ogre.framework headers as well.

In the Samples.xcodproj of the latest SDK Sinbad has worked out a method using symbolic links to link against the correct framework, build or release, automatically. Check it out.

Tricky Fly Blog

OS X Ogre Eihort SDK

About this entry

Comments are closed

About

Recently

Categories

Pages