Resource Provider: Memory Manager issues & breaking the publ

[CrazyEddie]

This is mainly just a note to say that last night I did some work to resolve the Ogre / Xerces memory manager conflict, and removed the public dependency on Xerces-C++. Basically, removing the dependency is the important bit, as once this is done the memory manager conflict is a non-issue.

To this end, I have made some changes locally to remove InputSourceContainer. My fix is loading all data via the loadRawDataContainer method, any part of the system that needs to pass this to xerces deals with this as part of the implementation; it adds about 3 lines of code per use of xerces.

I'm still doing some testing on this, and will not commit until after _mental_ has committed the Ogre 1.0 fixes to the resource provider system.

Any comments in the mean time are welcome

CE.

[_mental_]

Any chance you could post a diff of the changes?

[CrazyEddie]

The entire thing, including the removed parts, is quite large, so rather than post in-line I'll link to it:

It's The Diff

It hasn't had extensive testing as I've been tied up with other things, but it does seem to do the job okay.

CE.

[_mental_]

Its not as elegant (IMHO), but does the trick

[CrazyEddie]

Yeah, in many ways I'd much prefer to leave things alone, though the conflict that xerces causes with Ogre is a real pain in the rear. 'Nice' alternatives to this are a little thin on the ground.

I'll make a final decision on this today or tomorrow, though at the moment I am leaning towards using this solution; if only so I don't have to keep telling people to shuffle their includes around