OgreProfiler - avoid recompilation of Ogre

Anything and everything that's related to OGRE or the wider graphics field that doesn't fit into the other forums.
Post Reply
Posts: 11
Joined: Sat Feb 12, 2005 12:39 am
Location: Sweden

OgreProfiler - avoid recompilation of Ogre

Post by grimm »

Currently when using the OgreProfiler, in order to enable or disable profiling we need to set the OGRE_PROFILING flag in OgreConfig.h and recompile Ogre. This flag is used to decide if the OgreProfiler singleton object is created in OgreRoot.

My suggestion is to remove the OGRE_PROFILING from OgreConfig.h and let the applications set this flag themselves. Then we can enable or disable profiling without recompiling Ogre. Since OgreProfiler seems to be a very cheap object to construct, I think it can be created in either case.

I think that the only reason for having a profiling flag in Ogre, would be if this enable profiling of Ogre itself.

Post Reply