Pages: [1]   Go Down

Author Topic: Visual Studio.NET 2003  (Read 3660 times)

rbottoms

  • Posts: 7
  • Turrets: +0/-0
Visual Studio.NET 2003
« on: December 19, 2005, 05:12:36 pm »
Has anyone got the code base working in Visual Studio.NET 2003? I'd like to use DLL's instead of the virtual machines. The game code compiles to a dll with no problem, but cgame & ui fail with a bunch of errors.

Linking...
ui_shared.obj : error LNK2001: unresolved external symbol _va
ui_atoms.obj : error LNK2019: unresolved external symbol _va referenced in function _Com_Error
ui_gameinfo.obj : error LNK2001: unresolved external symbol _va

<snip>

thx
Logged

rbottoms

  • Posts: 7
  • Turrets: +0/-0
Visual Studio.NET 2003
« Reply #1 on: December 28, 2005, 04:44:52 am »
Third time's the charm.


The problem was build order.
Logged

rbottoms

  • Posts: 7
  • Turrets: +0/-0
Visual Studio.NET 2003
« Reply #2 on: December 30, 2005, 06:03:19 pm »
I've gotten cgame, game & qauke.exe to compile. The UI portion seems to be a bit recalcitrant but I think I'll get it done today.
Logged

rbottoms

  • Posts: 7
  • Turrets: +0/-0
Visual Studio.NET 2003
« Reply #3 on: December 30, 2005, 10:27:10 pm »
Got all three working. DLL all the way now.
Logged

Who

  • Administrator
  • Posts: 253
  • Turrets: +36/-22
Visual Studio.NET 2003
« Reply #4 on: December 30, 2005, 11:33:17 pm »
have you tried doing it in windows on a command line?

like
C:\> Compile C:\Tremulous\Source

?
Logged

rbottoms

  • Posts: 7
  • Turrets: +0/-0
Visual Studio.NET 2003
« Reply #5 on: December 31, 2005, 08:03:47 am »
I do most of my command line work under Linux. Windows is overall more IDE friendly and it's where most of the client side work I am doing happens. (our end product will support Win32/OSX/Linux client wise)

I am much more concerned with performance and setup issues on the server side where I've had minimal trouble compiling the package.
Logged
Pages: [1]   Go Up