Game Development Community

Anyone tried compiling the engine with C++.NET?

by Andreas Papathanasis · in Torque Game Engine · 02/19/2002 (2:23 am) · 9 replies

Yesterday night i got the engine and tried to compile it using Visual C++.NET, microsoft saying most projects don't need any changes and all that :) Problem is, i got numerous error messages when trying to compile the demo application. Has anyone else tried this? I hadn't the chance to go into many details yesterday, but hopefully sometime soon i will, just wondering if someone can save me some time.

#1
02/19/2002 (9:49 am)
Here's the problem: the assembly files require special build calls to NASM. All you have to do to fix this is to put those calls in double quotes. Say the call was:

nasm blah

just make it

"nasm blah"
#2
02/19/2002 (11:37 am)
Ok now, you've got me. When I tried it compiled fine! Hmmmm. I have a feeling a lot of the asm was moved into C code for cross platform development.

However this might also be the cause of some of the stranger bugs i've been getting.
#3
02/20/2002 (9:10 pm)
can someone please be more specific this is a problem i have and i would really like to be able to complile
#4
02/21/2002 (7:09 am)
please??
#5
02/21/2002 (8:14 am)
When IU tried to build the Torue-Engine under .Net. I also gut numerous error messages. One saying that ctl3d.h is missing. If you get the Same use the ctl3d.h from your VC++ 6 and it will work.
#6
02/21/2002 (8:26 am)
this is odd,
I just did a fresh install of XP Pro, VS .NET (latest from MSDN), XP Office and then the torque engine.
compiled clean outof box without a glitch.
are you sure the entire framework was installed? latest updates etc..?


-Ron
#7
02/21/2002 (11:58 am)
the problem seems to be with the special build instructions for the asm
files. I copied nasm where it should be but it still gives me an error

something like there is multiple input files or something. The error
seems to be coming directly from nasm itself.

Thanx for your help
#8
02/22/2002 (12:48 pm)
I figured it out for myself. If anyone else wants to know to compile under visual studio .NET or VC7

change all the .asm custom build setup string to

nasmw.exe "$(InputPath)" -f win32 -o "$(IntDir)/$(InputName).obj"

thats it
#9
02/22/2002 (1:08 pm)
wierd,
wonder why I did not have to-do that?
the CVS 1.1.1 release compiled clean without
any modifications to the .sln etc..

-Ron