se5a wrote:On that note though, what would it take to get it to compile for "AnyCPU"?
se5a wrote:Yeah, the full version of VS allows plugins, and some tools for working with a larger team.
BrainScan wrote:I've spent the last few days working on it and I now have 1.8.1 "working". Essentially, I had to disable [...]
But I have it up and running with my current project now.
BrainScan wrote:What exactly is required for contributing these change back?
I know the main Ogre project requires a contributor agreement be filled out. Anything like that here?
BrainScan wrote:I'm not familiar with Hg at all for source control, so it make take me some time to be able to push any changes. Do we need a new branch? Should the auto-wrapper be able to wrap both versions or do we stop development on 1.7.4 and just move forward
BrainScan wrote:Now Ogre has switched to the MIT license, but most of the Mogre files still have LGPL headers.
BrainScan wrote:there will be some breaking changes
Beauty wrote:Download the current Mogre repository and create a new branch (e.g. name "Mogre 1.8").
Then commit all your changes and upload the modified repository to your BitBucket account.
So everybody can see your changes and it's easy to push them to the official Mogre repository.
Beauty wrote:Did you use the MogreBuilder?
If yes, did you apply changes / additions to the code?
Beauty wrote:BrainScan wrote:there will be some breaking changes
It would be nice if you write some details.
Are the changed caused by Ogre (API changes) or something related to the Mogre wrapper?
BrainScan wrote: I still need to find a nice Hg client for windows and figure it all out.
Beauty wrote:I don't think x64 is important for most users. If somebody needs it, he can compile it by the -64 option of MogreBuilder and include the binaries to his project.
An other point: Which Visual Studio version should be offered? VS 2010 or 2012 or both.
You want to do much. Ogre update, add-ons update, SDK update ... this is too much for one person at one time.
Pitancos wrote:Cool news! But one question, BrainScan: you said you removed the terrain and paging components, do you plan to include them again? I think they are a really important part of Ogre 1.8+. Especially the paging system can be really powerful.
Pitancos wrote:What is missing for Mogre 1.7.4? The terrain and paging component are wrapped but are they fully working? Samples do work, I know and tested, but what is still missing? Which features are missing that exist in the corresponding Ogre version? I took a look at the bug tracker but those are not especially problems relating to the current version (meaning no missing features) but general bugs (should be fixed anyway).
Pitancos wrote:Does anyone ever had the error LNK2034? I appears only when I am compiling Mogre for .NET3.5 in debug mode (both in x86 and x64), the release mode works fine. It is poorly documented or I am just too stupid to find the right sources on the internet...
se5a wrote:Edit: reading a bit more, it seems that CXXI was looking very promising a few years ago... then nothing.
though looks like this branch of it has had activity six months ago: https://github.com/tritao/CppSharp
Users browsing this forum: No registered users and 1 guest