Mogre SDK development

[kwertz]

Inserted by moderator:

This thread is for improving of the Mogre SDK (currently related to 1.6.4).

The Mogre SDK should be user friendly, especially for newcomers.

It should:
* check for installed Mogre depencies
* offer installation of needed depencies
* install the Mogre SDK (in best case without need of manual system changes)
* contain different libraries
* contain sample applications

In the wiki is the page Mogre SDK development is an overview for the important points and links.

The discussion started in thread Mogre 1.6.4.
Now it follows up here.


Downloads:
* SDK: The newest release of MOGRE SDK you find at http://mogresdk.googlecode.com
* Binary and lib only: here in SVN of Mogre SDK (look to bin and lib directory)

SVN:
* Direct SVN link: http://mogresdk.googlecode.com/svn/trunk
To get write access ask user kwertz.

Moderator note:
Most of the posts were in thread Mogre 1.6.4.
Now they are moved to this thread.

Here the first SDK related post (by user kwertz)
=============================================================


I would like to announce that I created a windows installer for the new MOGRE 1.6.4 Beta bugfix 1.

Download it here: MOGRE SDK 1.6.4 Beta Installer.

The installed folder contains the following files and folders:

• D: bin - Contains the MOGRE binaries (debug and release)
• D: includes - Contains the include files to compile plugins against MOGRE
• D: Lib - Contains the static library files of MOGRE
• D: Media - Contains the media files required to run the MOGRE demos which can be compiled with the "BuildSamples.cmd" command script (see below)
• D: Samples - Contains the source code of the MOGRE samples
• BuildSamples.cmd - Lets you build the MOGRE samples with only one click
• ChangeLog.txt - This is the change log
• License.html - Contains the LGPL license text
• MOGRE SDK.url - This is a link to the MOGRE homepage
• MogreSamples.sln - The solution containing the sample projects
• ReadMe.txt - This provides an overview of the MOGRE SDK. Read it!

Please test the installer as well as the installed SDK and give feedback!

For those interested: You can also download the installer script (Inno Setup, not NSIS). In order to do that, please browse to this folder.

[GantZ]

well done !, the one click build for sample is really convenient .

the Mogre project was really lacking of a decent recent SDK. i also think that we will soon be able to step away from the "beta" release state to a stable release, so we can replace the old 1.4.8 SDK with a new 1.6 one.

just a question, which version of MogreNewt have you include in the project ? it seem to be a rather old one.

[kwertz]

The one from the 1.4.8 SDK, but I think it should work with 1.6.4 too.

[GantZ]

MogreNewt is specifically linked to an ogre version, so it will not work. also, could you remove the PCZSceneManager and the octreezone plugin ?, this thread remind me they are not working in Mogre ATM.

[kwertz]

MogreNewt is specifically linked to an ogre version, so it will not work. also, could you remove the PCZSceneManager and the octreezone plugin ?, this thread remind me they are not working in Mogre ATM.

Okay, update done. Please check if everything is correct now. You can download the new SDK from the usual place.

[GantZ]

just check it, everything ok. thanks !

[hedphelym]

Check all needed dlls are present in your output folder where compiled exe file placed. I.e. Mogre.dll OgreMain.dll ... Look here for detailed info: http://www.ogre3d.org/addonforums/viewtopic.php?p=65076#p65076

If i install the sdk, then use the "build.bat" it builds everything, and i can then run the exe's directly from the release dir.

i then open the sample solution in my IDE (VS), and compile it (Release x86) , it gives these exceptions.

[GantZ]

what is the output folder in the build tab of your VS project properties ? you should have ..\..\bin\release\ (or debug given your configuration) as output folder.

there is a post build event that copy all exe to the bin folder of the sdk, so it could be that when in VS, it try to run the version in the bin folder of the project you try to debug, not the one of the SDK, do you have a .vshost.exe for the sample you try to run in the release dir of the SDK ?

[Ricane]

@hedphelym: Got the same problem; the solution for me was to set the "Platform target" to "Any CPU" and the "Output Path" to "..\..\bin\release\" (both in the Properties screen of the projects).

After doing so, everything could be build and executed out of VS.



Regards from Germany,

Ricane

[hedphelym]

argh, now i get this instead:

Code: Select all

System.Runtime.InteropServices.SEHException was unhandled
  Message=External component has thrown an exception.
  Source=Mogre
  ErrorCode=-2147467259
  StackTrace:
       at Ogre.ConfigFile.load(ConfigFile* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , Boolean )
       at Mogre.ConfigFile.Load(String filename, String separators, Boolean trimWhitespace)
       at Mogre.Demo.MogreForm.OgreWindow.InitMogre() in C:\MogreSDK 164\Samples\MogreForm\MogreForm.cs:line 65
       at Mogre.Demo.MogreForm.MogreForm..ctor() in C:\MogreSDK 164\Samples\MogreForm\MogreForm.cs:line 22
       at Mogre.Demo.MogreForm.Program.Main() in C:\MogreSDK 164\Samples\MogreForm\Program.cs:line 17
       at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:



[hedphelym]

took away the post build "copy" event.
pointed the output to :
c:\mogresdk\bin\release

It does now work.

[kwertz]

Late, isn't it?

Okay, I updated the 1.6.4 SDK.

Changes:

• Removed "copy ..." command from the post-build events.
• Target platform changed to "Any CPU" in file "BuildSamples.cmd".
• Created a new file called "BuildSamplesX86.cmd".

I think, this should fix the problems described in the posts above. If it does not, please report the issue/-s (describe them in detail).

[hedphelym]

Thanks,
I will try this tomorrow, and report back!

[Beauty]

If there isn't an example for Mogre GUIs, it would be nice to add some of them to the SDK.
I suppose many users (also new ones) want to use a GUI system.

Miyagi is looking well and powerful.
Also it's actively developed (by smiley80).
We can ask smiley80 for an example application.
http://www.ogre3d.org/wiki/index.php/Miyagi
viewtopic.php?f=8&t=9025

Alternatives are
ButtonGUI - http://www.ogre3d.org/wiki/index.php/ButtonGUI
MQuickGUI - http://www.ogre3d.org/wiki/index.php/MQuickGUI
MogreBetaGUI - http://www.ogre3d.org/wiki/index.php/MogreBetaGUI (I had problems with it and debugging wasn't easy because of crypted variable names)
Mogre CEGUI - http://www.ogre3d.org/wiki/index.php/Mogre_CEGUI (I think this was outdated)

If I forgot important ones (for Mogre), please tell me.

[hedphelym]

I second all of this, it would help us very very much!