Requesting a pointer to info....

Compiling the source for the ogre exporter (VS2008, Ogre 1.7.2, boost 1.45, etc...)

The late 40's are playing with my eyesight, but is there a readme or info on build settings or expected layout?

I'm seeing complaints regarding boost date_time at the point Ogre.h is included in, say, blendshape.cpp compilation, but that isn't a problem building ogre itself (or ogre applications).

Permalink

We don't use boost and we're still using Ogre 1.7.1, so maybe that's it. I can say it compiles fine with no issues for us. You may have warnings since Ogre itself doesn't compile in Warning Level 4, but there shouldn't be any errors.

Permalink

While the export source doesn't use boost, once ogre.h is included, since ogre is dependent on boost, it has to be there and ogre's use of it has to be appeased.

The errors I'm getting relate to boost's date_time library, but some research suggests this is a build configuration issue.

The first couple of complaints are:

1>d:\development\boost_1_45_0\boost\date_time\gregorian\greg_duration.hpp(37) : error C2676: binary '&' : 'boost::gregorian::date_duration::duration_rep' does not define this operator or a conversion to a type acceptable to the predefined operator

1>d:\development\boost_1_45_0\boost\date_time\gregorian\greg_duration.hpp(37) : error C2351: obsolete C++ constructor initialization syntax

1>d:\development\boost_1_45_0\boost\date_time\gregorian\greg_duration.hpp(37) : error C2512: 'boost::date_time::date_duration' : no appropriate default constructor available

Which don't really tell much because by the time this code is being processed, the error (probably the definition of the typedef duration_rep and it's relatives) already occurred, and THAT is probably because of something misconfigured with respect to ogre.

One document suggested it was known to be an issue in some configurations where STLPort doesn't support wchar_t, yet the project is compiled using wchar_t. Alas, that doesn't appear to apply, but something in that neighborhood must.

I'll load the 1.7.1 source and try that. In theory Ogre should be stable from 1.7.1 to 1.7.2, but that's just theory.

Permalink

We compile Ogre from its stock source code in-house and disable its boost support. Looking at the Ogre forums it seems Ogre has had its fair share of boost issues. You'll have better luck on the Ogre forums as this is a general Ogre configuration issue.