Compiling problem
by Casey Weidner · in Torque Game Engine · 03/23/2006 (8:24 am) · 4 replies
Hi, I'm using visual studio .net 7.0, and I cant seem to get torque to compile any more. I was adding some of the inventory resorces and object selection resource to a clean copy of 1.4, and all was working untill I did a complete clean of all the projects in the solution. Now when I try to compile the engine or the engine lib, I get a nasmw error saying can not parse multiple objects. But when downloaded and installed a clean copy of torque it worked fine... Any idea what may cause this?
Thanks,
Casey
Thanks,
Casey
#2
Casey
03/23/2006 (10:07 am)
If i had more information i could probably figure it out my self. i dont know much about VS .net, im thinking i need to reinstall VS6 and see if i can get that to work. i still dont understand why nasmw wont run. i didnt do anything to the asembly source, i added a couple lines of code to the resource manager, a couple files for guiobjectview and the code of the object selection. it seems to have gone bonkers after the object selection. but it did compile after i put in the code. then i switched over to release for shits and gigles and thats when it stoped compiling. BUT i put it back to debug and i still wont compile. im kinda confused about it.. but i also had been up for 19 hours at this point so i might have been over looking something. is there any specific information that would be helpful to solve this!Casey
#3
sounds like perhaps the custom build options for the file got borked?
03/23/2006 (10:16 am)
Lets have the actual error provided by the compiler output is what I meant :)sounds like perhaps the custom build options for the file got borked?
#4
03/23/2006 (12:24 pm)
Yes, it is complaining about the custom build.. im currently at work.. and then dont get home from class untill 8pm tonight.. but when i get home i will post the exact error it is giving me
Torque Owner Badguy
Without more information I'm afraid the only people that can help you
are the ones that have had the same problem.