Mogre 1.8

Hi all!
I know that ogre 1.8 is still RC, but did someone tried to create mogre for ogre 1.8?
thanks again!

I'm not sure if anyone as already tried but it's theoretically very easy with the MogreBuilder. Mogre info here, here and here.

I am waiting.
Hopefully we can pull down as a binary file.

I am waiting.
Hopefully we can pull down as a binary file.
Why do you need to wait? Why can't you do it yourself? If you have problems there are always people willing to help. But its unlikely anyone will do it unless they have a good reason.

I am amateur. Maybe you could be in the future.

I am amateur. Maybe you could be in the future.
Everyone is an amateaur until they are not. You might be surprised how easy it is with MogreBuilder.

Does MogreBuilder compatible with Mogre v1.8?

Does MogreBuilder compatible with Mogre v1.8?
MogreBuilder is a build tool for building every version of Mogre. You use a configuration file to setup what version of Mogre you would like to build and run the builder. I haven't personally used it to build Mogre 1.8 but I can't see any reason why it wouldn't work. Perhaps you will be the first to do it.

Do I still need the ClrPatchFile and CygonPatchFile?

Does the Dependencies url need to be changed?

What if I don't want MogreNewt?

EDIT: also I got a whole bunch of warnings saying "Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

Do I still need the ClrPatchFile and CygonPatchFile?
Does the Dependencies url need to be changed?
What if I don't want MogreNewt?
Beauty changed a bunch of things since the last time I used the MogreBuilder (like adding support for MogreNewt). You might want to check this forum topic and the instructions on the bitbucket page. As far as I know everything should work just fine if you follow the instructions on bitbucket.

Also, I only just realised today that Ogre 1.8 has been officially release. I'm sure someone will get around to updating Mogre soon enough if you are still having trouble.

Does MogreBuilder compatible with Mogre v1.8?
MogreBuilder is a build tool for building every version of Mogre. You use a configuration file to setup what version of Mogre you would like to build and run the builder. I haven't personally used it to build Mogre 1.8 but I can't see any reason why it wouldn't work. Perhaps you will be the first to do it.

I'm wondering, who told you it would work for 1.8? Fact is, MogreBuilder is just a tool to make it easier to build Mogre, because a lot of tedious steps are necessary to do so. But it won't work for 1.8, not even for any other version of Ogre than the one is was made for.

To make Mogre compatible with Ogre 1.8, a lot of steps are necessary. Most of them far from trivial. The patches need to be updated to the new version and from my past experiences I can say, it's very unlikely that the wrapper generator will cover all changes in the code without some tweaking.

So please don't tell people that it will work with 1.8 without even trying it yourself. You made Pyritie waste a lot of time.

So please don't tell people that it will work with 1.8 without even trying it yourself. You made Pyritie waste a lot of time.
I wouldn't really call 15-20 minutes a lot of time :D

I'm wondering, who told you it would work for 1.8? Fact is, MogreBuilder is just a tool to make it easier to build Mogre, because a lot of tedious steps are necessary to do so. But it won't work for 1.8, not even for any other version of Ogre than the one is was made for.
I spent a few weeks making changes to MogreBuilder to make it much easier to use including adding the ability to use a configuration file to setup different build configurations. I created a 4 part series on my blog about the changes I made to MogreBuilder to make it better, you can find the series and discussion in this forum topic.

I'm not denying that I don't know exactly what changes are required to build Mogre 1.8 but in theory it could be as simple as changing the OgreBranch in the configuration file from v1-7 to v1-8. Of course, there was no way of knowing exactly what else needs to change without further investigation. I got the impression Pyritie wanted to try it.

To make Mogre compatible with Ogre 1.8, a lot of steps are necessary. Most of them far from trivial. The patches need to be updated to the new version and from my past experiences I can say, it's very unlikely that the wrapper generator will cover all changes in the code without some tweaking.
Do you know what steps are necessary? If you have past experience using MogreBuilder to buld Mogre 1.8 you might be able to help. If you have already updated the patches you could help even more by putting your changes in the bitbucket repository.

So please don't tell people that it will work with 1.8 without even trying it yourself. You made Pyritie waste a lot of time.
I'm sorry if my comments were misleading. I clearly stated that I haven't personally used MogreBuilder to build Mogre 1.8. All I said was that I don't know of any reason why it wouldn't work. As far as I know, nobody has tried to use it to build Mogre 1.8 and I also clearly stated that Pyritie might be the first to do it.

And just to be clear, I stand by my comment that MogreBuilder is a build tool for building every version of Mogre. It was used to build several previous versions of Mogre and it will be used to build future versions of Mogre. I never said it was perfect, there is no such thing. If there is any reason why it doesn't work it will be fixed.

Anyone had any luck with this yet?

I haven't been very active lately, but I still read the forums from time to time. I doubt running any type of automated tool will be possible for Ogre 1.8 without significant wrapping work first. The main reason for that is the custom wrapping that must occur on Ogre core classes. I imagine some of these classes have changed from 1.7, and this would imply wrapping changes (i.e. changes to the C++ classes / mapping files to support the wrapping paradigm used). I custom wrapped three libraries from scratch myself - PagedGeometry, OgreSpeedTree, and SkyX 3.x. This is something that required a significant knowledge of the wrapping methodologies and a lot of trial and error. Building the thing is easy - wrapping is the hard part .

Now, the core classes might have changed so little that this may not be necessary for Ogre 1.8 and simply patching those files with the 1.7 wrapping patch might do it. I highly doubt it.

I haven't been very active lately, but I still read the forums from time to time. I doubt running any type of automated tool will be possible for Ogre 1.8 without significant wrapping work first. The main reason for that is the custom wrapping that must occur on Ogre core classes. I imagine some of these classes have changed from 1.7, and this would imply wrapping changes (i.e. changes to the C++ classes / mapping files to support the wrapping paradigm used). I custom wrapped three libraries from scratch myself - PagedGeometry, OgreSpeedTree, and SkyX 3.x. This is something that required a significant knowledge of the wrapping methodologies and a lot of trial and error. Building the thing is easy - wrapping is the hard part .

Now, the core classes might have changed so little that this may not be necessary for Ogre 1.8 and simply patching those files with the 1.7 wrapping patch might do it. I highly doubt it.
Thanks DirtyHippy, that's probably the clearest explanation I've seen on this topic. The fact is, the difficultly of this task is not really known without trying it or doing some heavy investigation beforehand into the changes made between each version of Ogre. In an ideal world, this would be supported by the core Ogre team, but I'm not sure if the reality is that clear cut.

Another thing we can do to improve this situation is setup an continuous integration system. There was some talk about this a while back, the idea was to run the MogreBuilder over the latest Ogre sources daily and report failures sooner. It's not a perfect solution but at least it would make it easier to keep them in sync.

...anyone?

...anyone?
Keep an eye on this topic. If anyone is going to build mogre 1.8 it is likely to be discussed over there.