Page 1 of 1

Problems with Visual Studio .NET (7.0)

Posted: Mon Feb 14, 2005 9:58 am
by Tx3
I have successfully built Ogre3d files.. libs and Examples. Problems came when I tried to create my own project with VS.net. I have tried many source codes and project settings are taken from this tutorial --> http://www.ogre3d.org/docs/Tutorials/2_ ... Index.html

I'm using Ogre 1.0RC

This is the error I got:
c:\ogre3d\ogrenew\samples\common\include\exampleapplication.h(75): fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\9466\vc\Compiler\Utc\src\P2\main.c', line 146)
---


Another problem came when I tried this Visual Studio AppWizard which is in Other/ directory.

c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(132): error C2664: 'Ogre::Camera::pitch' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(111): error C2664: 'Ogre::Camera::yaw' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(115): error C2664: 'Ogre::Camera::yaw' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(131): error C2664: 'Ogre::Camera::yaw' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(139): error C2664: 'Ogre::SceneNode::yaw' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(143): error C2664: 'Ogre::SceneNode::yaw' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(147): error C2664: 'Ogre::Node::pitch' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(151): error C2664: 'Ogre::Node::pitch' : cannot convert parameter 1 from 'float' to 'const Ogre::Radian &'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(158): error C2039: 'setStatsDisplay' : is not a member of 'Ogre::RenderWindow'
c:\ogre3d\ogrenew\Samples\OgreDemo2\include\OgreDemo2FrameListener.h(162): error C2039: 'setStatsDisplay' : is not a member of 'Ogre::RenderWindow'

Posted: Mon Feb 14, 2005 10:03 am
by epopov
You can try to have a look here (even if it's for VC6): http://www.ogre3d.org/phpBB2/viewtopic. ... iler+error

Posted: Mon Feb 14, 2005 10:11 am
by haffax
The tutorial isn't uptodate, you have to change the code a bit. Look here for details. (Hint: back then SceneNode used Degree values, Quaternion Radian values)

Posted: Mon Feb 14, 2005 5:22 pm
by Tx3
Using /Zm500 or /Zm1000 didn't help for this error:

c:\ogre3d\ogrenew\samples\common\include\exampleapplication.h(75): fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'f:\vs70builds\9466\vc\Compiler\Utc\src\P2\main.c', line 146)

Any suggestions? I'm stuck... :(

Posted: Mon Feb 14, 2005 5:28 pm
by haffax
Tx3, have you the latest service pack for Visual C++ 6 installed? If not, do so. I know there was an internal compiler error problem when you don't have it.

Posted: Mon Feb 14, 2005 5:37 pm
by Tx3
But I'm using .NET (version 7.0)

Posted: Mon Feb 14, 2005 5:45 pm
by haffax
I see it now. :oops:
Then I have no idea, sorry.

Posted: Mon Feb 14, 2005 7:59 pm
by epopov
'INTERNAL COMPILER ERROR' errors are very annoying because you don't know what the problem really is. Generally, when one shows up, you have to either reorganize your source file or add / delete some code. Obviously, it's not very easy in that case because it's a 'third-party' code.
Have you tried to have a look into msdn, looking for possible causes of 'internal compiler error' ?
Others use VC7.0 with no problem (Sinbad, for one). May be you have not enough RAM ? or free disk space ?

Posted: Mon Feb 14, 2005 11:14 pm
by sinbad
I normally find a clean build will sort out an internal compiler error when it crops up, or if it doesn't it's because it's a particularly nasty use of templates which I reorganise.