Re: Ogre Bindings and VS11
Posted: 22 Aug 2013, 17:35
Hi!
The reason of having OgreBindings in github is because we want people to collaborate and improve the code. This project started from the Ogre team and I have been doing patches to maintain compatibility with each version of NoesisGUI.
The initial idea was having a small static library that wraps NoesisGUI. In this library there should be no dependencies with absolute paths. All I see is dependencies to headers starting with "../". Being a static library you can integrate it as you would do with any other static library. I personally prefer not copying things and linking directly to the library found in the output directory of the OgreBindings.
Apart from linking to this static library you need copying Noesis binaries (dlls) to the location of the main executable. With that and the cache of resources your application should work fine. Are you still having problem?
About the problem with the window. Yes, the implementation could be improved and accept an external window. If you want I can give you write access to the repository to improve all this. Or you can pass me a patch and I will commit it.
The other two sample projects can be ignored. They are only there as samples.
I don't know it this solved your doubts. I hope so.
The reason of having OgreBindings in github is because we want people to collaborate and improve the code. This project started from the Ogre team and I have been doing patches to maintain compatibility with each version of NoesisGUI.
The initial idea was having a small static library that wraps NoesisGUI. In this library there should be no dependencies with absolute paths. All I see is dependencies to headers starting with "../". Being a static library you can integrate it as you would do with any other static library. I personally prefer not copying things and linking directly to the library found in the output directory of the OgreBindings.
Apart from linking to this static library you need copying Noesis binaries (dlls) to the location of the main executable. With that and the cache of resources your application should work fine. Are you still having problem?
About the problem with the window. Yes, the implementation could be improved and accept an external window. If you want I can give you write access to the repository to improve all this. Or you can pass me a patch and I will commit it.
The other two sample projects can be ignored. They are only there as samples.
I don't know it this solved your doubts. I hope so.