alberts
22-11-2005 18:02:44
Hi
I finally could compile ODN this morning. I tell you what I have done to compile the sources, because I think the wiky explanation is not enough for the newbies:
First, I installed VS.NET 2003. You need to select c++ and c# to install. None of the c# subcomponents is needed, but you need to select all of the c++ subcomponents (the tools subcomponent is not actually needed). If you don’t select the c++ subcomponents you will get an error in the output window (not the task window) saying that the “casser” file could not be opened. This error doesn’t stop the compile process, so you have to review the entire text in the output window.
Then I download the prebuilt ogre sdk 1.0.4 version from http://prdownloads.sourceforge.net/ogre/OgreSDKSetup1.0.4_VC71.exe?download and install it.
To retrieve the content of the CVS I used TortoiseCVS, which can be downloaded from http://www.tortoisecvs.org/. After the installation I clicked with the right button over an explorer window and choose “CVS Checkout…” at the popup menu. At the TortoiseCVS window I entered these values:
Protocol: Password server (:pserver:)
Protocol parameters :
Server: cvs.sourceforge.net
Port:
Repository folder : /cvsroot/ogre
User name : anonymous
Module: ogreaddons/ogredotnet
When you push the OK button all the CVS contents are downloaded to a new directory.
I downloaded SWIG from http://prdownloads.sourceforge.net/swig/swigwin-1.3.27.zip and unzip it. Then I set the SWIG_HOME environment variable like is described in the wiki:
Right click on My Computer
Click Properties
Go to the Advanced tab
Click on Environment Variables button
Under User Variables click on New
Put SWIG_HOME as the name of the new environment variable
Under the variable VALUE, put the path to where SWIG.EXE is (without a trailing slash).
Example: “C:\Path\To\Swig”
NOT: “C:\Path\To\Swig\”
Then I opened the OgreDotNet solution in the ogredotnet directory and right clicked on Ceguibindings.i and selected Compile to generate the .cs files from the .i files. Did the same for the OgreBindings.i and OgreBindings_Cegui.i in that order. After that I closed and reopened the solution, so the missing file errors were out. There were two files that I had to exclude (delete) from the “ceguinet” project manually: SWIGTYPE_p_utf32.cs and SWIGTYPE_p_utf8.cs. There were three files that I had to add to the “OgreNet” project manually: SharedMaterialPtr.cs, SharedMeshPtr.cs and SharedSkeletonPtr.cs. I don’t know why these files are not in the project.
Finally, I built the entire solution and it produced seven .dll files and tons of warnings messages (but no errors).
To develop a C# Ogre application I create a new blank solution and copy all the .dll files generated by the ogredotnet solution into the \bin\debug directory of the new project. I copy into the same directory all of the files (*.dll, *.cfg,…) in $OGRE_SDK\bin\debug directory. Then, I add a reference in the project to the following .dll files: CeguiDotNet, Math3D, OgreDotNet and OgreDotNet.Cegui.
If you are working with the examples provided, you have to copy the $OGRE_SDK\media directory into the new project one too (the media directory should be at the same level of the bin directory). If you don’t do this properly your application will produce an error while trying to create the resource group bootstrap (see the msdos console).
I prefer to start a new application modifying the source code of the exampleApplication.cs file, instead of inheriting from the exampleApplication class (you have to rename the class, add a main method and remove the abstract keywords).
If you still cant compile the sources or you only need the ODN prebuilt binaries I've put it in http://www.ugr.es/~agsh/ogre/prebuilt_ogreDotNet_binaries-11-22-2005.rar. The version published by maleficus in this thread is not an up to date version (i think).
I hope this explanation helps to someone and I apologize for my english (my native language is spanish).
I finally could compile ODN this morning. I tell you what I have done to compile the sources, because I think the wiky explanation is not enough for the newbies:
First, I installed VS.NET 2003. You need to select c++ and c# to install. None of the c# subcomponents is needed, but you need to select all of the c++ subcomponents (the tools subcomponent is not actually needed). If you don’t select the c++ subcomponents you will get an error in the output window (not the task window) saying that the “casser” file could not be opened. This error doesn’t stop the compile process, so you have to review the entire text in the output window.
Then I download the prebuilt ogre sdk 1.0.4 version from http://prdownloads.sourceforge.net/ogre/OgreSDKSetup1.0.4_VC71.exe?download and install it.
To retrieve the content of the CVS I used TortoiseCVS, which can be downloaded from http://www.tortoisecvs.org/. After the installation I clicked with the right button over an explorer window and choose “CVS Checkout…” at the popup menu. At the TortoiseCVS window I entered these values:
Protocol: Password server (:pserver:)
Protocol parameters :
Server: cvs.sourceforge.net
Port:
Repository folder : /cvsroot/ogre
User name : anonymous
Module: ogreaddons/ogredotnet
When you push the OK button all the CVS contents are downloaded to a new directory.
I downloaded SWIG from http://prdownloads.sourceforge.net/swig/swigwin-1.3.27.zip and unzip it. Then I set the SWIG_HOME environment variable like is described in the wiki:
Right click on My Computer
Click Properties
Go to the Advanced tab
Click on Environment Variables button
Under User Variables click on New
Put SWIG_HOME as the name of the new environment variable
Under the variable VALUE, put the path to where SWIG.EXE is (without a trailing slash).
Example: “C:\Path\To\Swig”
NOT: “C:\Path\To\Swig\”
Then I opened the OgreDotNet solution in the ogredotnet directory and right clicked on Ceguibindings.i and selected Compile to generate the .cs files from the .i files. Did the same for the OgreBindings.i and OgreBindings_Cegui.i in that order. After that I closed and reopened the solution, so the missing file errors were out. There were two files that I had to exclude (delete) from the “ceguinet” project manually: SWIGTYPE_p_utf32.cs and SWIGTYPE_p_utf8.cs. There were three files that I had to add to the “OgreNet” project manually: SharedMaterialPtr.cs, SharedMeshPtr.cs and SharedSkeletonPtr.cs. I don’t know why these files are not in the project.
Finally, I built the entire solution and it produced seven .dll files and tons of warnings messages (but no errors).
To develop a C# Ogre application I create a new blank solution and copy all the .dll files generated by the ogredotnet solution into the \bin\debug directory of the new project. I copy into the same directory all of the files (*.dll, *.cfg,…) in $OGRE_SDK\bin\debug directory. Then, I add a reference in the project to the following .dll files: CeguiDotNet, Math3D, OgreDotNet and OgreDotNet.Cegui.
If you are working with the examples provided, you have to copy the $OGRE_SDK\media directory into the new project one too (the media directory should be at the same level of the bin directory). If you don’t do this properly your application will produce an error while trying to create the resource group bootstrap (see the msdos console).
I prefer to start a new application modifying the source code of the exampleApplication.cs file, instead of inheriting from the exampleApplication class (you have to rename the class, add a main method and remove the abstract keywords).
If you still cant compile the sources or you only need the ODN prebuilt binaries I've put it in http://www.ugr.es/~agsh/ogre/prebuilt_ogreDotNet_binaries-11-22-2005.rar. The version published by maleficus in this thread is not an up to date version (i think).
I hope this explanation helps to someone and I apologize for my english (my native language is spanish).
