eqemu won't compile on vs.net 2003

[alkrun]

Do you guys already know that the emulator won't compile on VS.NET 2003? Since you're still using the old C style includes for standard headers (which were deprecated in VS.NET, and now are fully removed in VS.NET 2003) it doesn't compile anything.

I don't mind going through the code again like I did lo those many months ago, but I don't want to do it if it's just going to be overlooked again. It's a waste of my time.

[dcl]

It compiles (it's what I use)

You just get a lot of warnings (which don't affect the executable)

[alkrun]

You get warnings in VS.NET. In the new version, VS.NET 2003 I promise you, it doesn't build. The warnings that you get in VS.NET about deprecated IO headers using C-Style includes mean that Microsoft planned on (and did) take the compatibility for the old include style out of VS.NET 2003.
[/b]

[Merth]

I can fix, but unfortunately <iostreams> is not part of earlier versions of visual studio (including vs.net 7.0). So I will have to use a precompiler statement to distinguish the versions - anyone know of a #define for VS IDE version? Or of a different way to handle this situation?

[alkrun]

#include <iostreams>

works in VS 6, VS.NET and VS.NET 2003. It works in gcc too. From what I remember there isn't a file in the include folder named iostreams without the extension in VS6, but the compiler knows how to handle it by adding the extension and namespace declarations.

[Merth]

What kind of magic did you do to get it to compile? Here's what I see:

#include <iostreams>

c:\EQEMUcvs\NewSource\zone\client_process.cpp(22 ) : fatal error C1083: Cannot open include file: 'iostreams': No such file or directory

[Merth]

Nevermind, I figured it out. The documentation says this, so that's why I went with <iostreams>

useoldio.h

/*
* Warning C4995, '_OLD_IOSTREAMS_ARE_DEPRECATED' is a deprecated name, is
* being issued because the old I/O Streams headers iostreams.h et al will no
* longer be supported from VC8. Replace references such as #include
* <iostreams.h> with #include <iostreams>, using the new, more conformant, I/O
* Streams headers.
*/


I used <iostream> and the warning went away.

[dcl]

Ah, my mistake.... for some reason I thought I was running 2003 on my home machine, since I run it on my work machine. Sorry :)

[alkrun]

No problem. And Merth, glad you got it working.

I've got a rough build of 5.0 dev running as the "Pollo Verde" server. It seems to be working ok except for some minor database problems (i.e. no items) but everything else looks good.

[Merth]

This has been fixed and will be effective on the next push out to CVS.

[websurf]

so I tried to change the includes to #include <iostreams>, and that would give me inc file not found.

and I also tried #include <iostream>, and this will give me tons of errors of cout, cin...etc being unidentified.

Any suggestions?

[Merth]

Change #include <iostream.h> to:

#include <iostream>
using namespace std;

There's one other ios header to change, and I think it's <fstream.h>. Do the same with this as with iostream.

[websurf]

cool, so that solves that prob.

Now its giving me linkage error when I try to compile zone.

LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification
client_process.obj : error LNK2019: unresolved external symbol "public: void __thiscall Doors::HandleClick(class Client *)" (?HandleClick@Doors@@QAEXPAVClient@@@Z) referenced in function "private: int __thiscall Client::HandlePacket(class APPLAYER const *)" (?HandlePacket@Client@@AAEHPBVAPPLAYER@@@Z)
zone.obj : error LNK2019: unresolved external symbol "public: __thiscall Doors::Doors(struct Door const *)" (??0Doors@@QAE@PBUDoor@@@Z) referenced in function "public: void __thiscall Zone::LoadZoneDoors(char const *)" (?LoadZoneDoors@Zone@@QAEXPBD@Z)
../build/ZoneDebug.exe : fatal error LNK1120: 2 unresolved externals


Plz give some advice.

[Edgar1898]

add doors.cpp and doors.h to your project

[websurf]

Ah, thanks.