Working in MOGRE 1.4.8

Yesterday i compiled MOGRE 1.4.7 finally with VS2008 and work very nice, also i update MogreNewt and fix some bugs in Mogre and MogreNewt.

But i notice that OGRE 1.4.8 was released too, then is better have last update and dont 1.4.7. Currently i am working on that..

Now we have a small problem, OGRE code is in a subversion server, and we cant update our ogre modifed code (using update special) because is in CVS format, i tried merge changes manually but that is very hard work, thats why i decide active CVS support in out MOGRE sourceforge project and copy there OGRE pure code, and then swicth our OGRE modifed code to this repository, in this way we can keep using CVS for update MOGRE.

For newies, MOGRE is in a Subversion server, but the OGRE files are in CVS repository, thats is why we need this change.

If someone knows a better way to update and merge a CVS repository with a Subversion repository just tell me..

yikes!!

Great! I'm eager to see a VS2008 version without dependencies to VC8 anymore.

ok i made it.. i could compile MOGRE 1.4.8, i making some test and creating a new solution for a easier way to compile mogre from source..

In this week official MogreSDK 1.4.8 will released.. yahoo!

Congrats Marioko.

I am away from Mogre & MQuickGUI now, but expecting to resume my activities soon.

My company merged with another one, now I am the manager of "Software Development Division" with 30 people at charge, so I am so busy these days.


Probably I will do my thesis for my Engineering in Information Systems around Mogre, I am defining the scope. Ideas are welcomed.

For newies, MOGRE is in a Subversion server, but the OGRE files are in CVS repository, thats is why we need this change.

If someone knows a better way to update and merge a CVS repository with a Subversion repository just tell me..
How about:

-creating a patch of the changes to Ogre's source (using TortoiseCVS)
-checkout the Ogre source from Ogre's SVN
-apply the patch (by TortoiseSVN)
-commit modified Ogre's source on Mogre's SVN

At a later time, in order to update Ogre's sources:

-at ogre source directory, set the SVN URL to point to Ogre's SVN (with 'Relocate')
-do a SVN update
-set the SVN URL back to Mogre's SVN
-commit changes

Will this work ?

Hey! Bekas is back!!!!

creating a patch of the changes to Ogre's source (using TortoiseCVS)
-checkout the Ogre source from Ogre's SVN
-apply the patch (by TortoiseSVN)
-commit modified Ogre's source on Mogre's SVN

At a later time, in order to update Ogre's sources:

-at ogre source directory, set the SVN URL to point to Ogre's SVN (with 'Relocate')
-do a SVN update
-set the SVN URL back to Mogre's SVN
-commit changes

Heyy that is a great idea.. i going to try that..

btw, bekas you only modify OgreMain???

ok, the SDK v1.4.8 is ready, tomorrow should be avaliable for download..

please wait..

Right on -- is this binary only or does it have source? And is it VC8 compatible or VC9 only?

Thanks!

BTW all of the build instructions talk about there being an ogrenew/ directory in trunk/ -- but that's not the case. Is it expected that someone building Mogre from source should run the wrapper generator on whatever version of Ogre they have? Or is there another reason that the ogrenew/ directory was removed from SVN? And of course it's no longer called "ogrenew", so...

It has binaries, libs, headers, and samples, is builded in VC9 but it should be compatible with VC8 (i think) because Mogre.dll is a Managed dll and is compatible with .NET 2.0 to .NET 3.5 framework.

The ogrenew folder was delete because i was making some changes, i will commit the new source with ogrenew right now, btw instructions for build mogre from source are deprecated now is a lot easier, wait the update.

"A lot easier" sounds awesome to me. It wasn't exceedingly painful to build before, but it was more than maybe it needed to be. Thanks again!

The ogrenew folder was deleted ...
Is it so important to keep it?

2) The 'ogrenew' folder will disappear from the path. It's a historical thing anyway, from when we reorganised the repository many, many years ago and replaced the old 'ogre' module. The Ogre code will now be found directly under the root of SVN.

I'm inquisitive, if I will have some problems again with the SDK *g*
But nice that you did it.

By the way ... nice to see you Bekas + welcome back

the SVN i ok now, is updated with last OGRE (include ogrenew) and all things.

Also Building from Source guide is updated. In this moment i am uploading MogreSDK_1.4.8, please wait..

The ogrenew folder was deleted ...
Is it so important to keep it?


Yes, because there are slight changes to the Ogre source tree to make it work in a CLR world.

btw, bekas you only modify OgreMain???
Yes.
instructions for build mogre from source are deprecated now is a lot easier
That sounds great.
BTW, if you haven't already, I'd suggest to disable "link time optimization" on Mogre's "Release" build. It increases build times with questionable benefits.. (I mean specifically for Mogre)

nice to see you Bekas + welcome back
Thanks!

It would be nice if (in future) the autowrapper would transfer XML comments for classes / members.