Building with vc 2005 express

#1 The only issue is the winnt.h issue. i dont have source code near me, but all it is is duplicating the DEFINE for PVOID64. that will fix it. a fancier way (what i did) was do a #ifdef for the first #define, which i am not sure would fix all combos, but hopefully yes.

hope that helps.

#2 Vs2005 Express setup by Matt Fairfax

#3 Thanks for the help guys. I had to do a little bit of interpretation to transpose the instructions for T2D, but I finally got it to work.

Edit:
I posted an updated list of steps at:
www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=5957

#4 Does PVOID64 need to be defined in winnt.h? can it just be commented out?
I read in another post that with compiling torque there is a problem using just the directx 8 files and not specifying the directx 9. pvoid64 is supposedly defined there as well.

I'm not using a 64bit processor and dont intend on using an app on one.

#5 I changed a line in winnt.h from #include to #include "basetsd.h" and now it doesnt seem to complain about line 222 (pvoid64) in winnt.h

now have unicode issues. will try tackling that.

#6 What i did was change my code to the following:

#ifndef POINTER_64
	typedef void * POINTER_64;
	#ifndef PVOID64
		typedef void * PVOID64;
	#endif
#else
	#ifndef PVOID64
		typedef void * POINTER_64 PVOID64;
	#endif
#endif

I dont know if i'm paranoid or crazy, but that works. (because some other projects I have complain if I have typedef void * POINTER_64;typedef void * PVOID64;

#7 Thanks for the info Jason.

I'm a bit confused on what that line of code is doing. (talking about the original line) I thought that it was trying to define pvoid64 as a pointer of type pointer_64.
From what i understand, using the " " form of the include will get the processor to look in the same directory as the current file first and then look in the specified include directories. The < > form doesnt seem to look at the current directory.
Since the " " form works for me, it indicates that I may not have my include structures set up properly.
(The basetsd.h file defines pointer_64).

Before I changed the #include line, I tried commenting out the typedef line and that caused a problem around line 5049.
After researching some more, I found the difference in the #include formats and used it.

#8 If all you are doing is T2D development, just change that line to be:

typedef void * POINTER_64;typedef void * PVOID64;

that is the only code change i had to do to get t2d building with vs2005 express. (just make sure you install the psdk)

#9 I'm having trouble running T2d in debug mode.. says "failed to open main.cs"

Any ideas?

#10 You need to tell VS where the projects executable is. Right click the project file and go to properties. Its listed in the Debug section.

#11 I belive you need to set your output path (under the linker section) to be ..\example

but... this should already be set if you are using the VC7 .sln as a starting point.

make sure you are using a clean, new install of t2d as your starting point. otherwise you'll run into more issues.

#12 Yes, the output path is set for all the projects. So, I guess this isn't a common thing, I didn't miss a step somewhere?

#13 Also, I dont know what this means, but when I run debug, the output window shows loading all kinds of stuff. It looks like its loading most or all .exe's in:
windows\system32
program files\belkin\nostromo
program files\yahoo\messenger

Of course the exe's in there dont have debugging symbols, but why the &*$% would it be trying to load that stuff? Obvously I have those paths set somewhere, but I sure don't know where.

In addition to all that stuff, it does load T2D_DEBUG.exe, but then exits when it can't find main.cs

#14 Also, i know that some people have problems if they open the .sln from within Visual Studio. Try double-clicking the .sln itself to open it.

also, if you are not, use C:\Torque2D\SDK as your sdk directory (if you are not already).. see if that helps

#15 Got it.. in the solution, I had to set the T2D project as "startup project". I think glu2d3d was set by default. Not sure about this... something other than T2D was anyway.

It's still trying to load all that other crap, and I'm not sure why. I get a long list of messages like:

'T2D_DEBUG.exe': Loaded 'C:\Torque 2D\SDK\example\T2D_DEBUG.exe', Symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\ntdll.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\user32.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\gdi32.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\winmm.dll', No symbols loaded.
'T2D_DEBUG.exe': Loaded 'C:\WINDOWS\system32\wsock32.dll', No symbols loaded.
...continues....

Any ideas about that?

#16 As for the PVOID64 error, all I did to solve it was to move the platform sdk includes/libs up to the top of the list in vc directories from tools->options.

Not sure if that was posted already or not.
joe.s

#17 Hello, im getting these errors, any ideas?

Error 1 error C3861: 'mClampResolutionVec': identifier not found d:\work\torque 2d\sdk\engine\t2d\fxtilemap2d.cc 2532


Error 2 error C3861: 'mClampResolutionVec': identifier not found d:\work\torque 2d\sdk\engine\t2d\fxtilemap2d.cc 2534

#18 Hey guys,

Not sure about your specific compiler issues with building because I do not currently use VS 2k5, however Melv has recently committed a new VC2k5 project file to SVN so you can be sure it will be in the next Alpha.

Regards,

-Justin

#19 In the next release, T2D will build in VC Express with a single click. I know this because I was the actual committer of the project file. Unless it doesn't work. Then it was Melv.

#20 Swine. ;)

- Melv.