New CVS dump Windows compile issues

[sonicintuition]

Greetings,

I downloaded the newest CVS dump of EQemu and was really excited to see that Lethal updated the project so that it would compile on windows. Unfortunately, it still refuses to compile, but this time for different reasons. EQmemshare.dll compiled fine with one warning. Cool. My problems lie in attempting compiles of world.exe and zone.exe (w/perl). I am using VS.NET 2K3.

When compiling world.exe, I get about 32 errors all having to do with EQnetwork.cpp. They are to the likes of "suchandsuch is not a member of EQstream". I figured I might just be missing a few files from the project, so I added the EQstream.cpp/.h because they weren't included - did not solve the problem. Is there some other files I need to add and if so, what?

When compiling zone.exe I get a whopping 435 errors. Many also had to do with the EQstream thing like above, and also most are (for example) like this:

C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\Include\WinSock2.h(1875): error C2375: 'ntohl' : redefinition; different linkage

I am assuming that I need to add something to the project, but I'm not sure and really confused. I've never had a problem with that type of error when compiling zone.exe in the past.

I've searched on this for a while and tried various things but nothing is working. I really hope its as simple as including files to the project. Any *helpful, polite* insight would be greatly appreciated. Thanks for your time.

Regards,
SI

[Facet42]

You need to remove the EQNetwork.cpp file from the project as it has been moved into the EQStream.cpp file if I remember correctly.

[sonicintuition]

Wow, thats it huh? Sheesh. Thanks a bunch. I'll edit this post if it works - just in case others run into the same issue.

EDIT: Okay, your solution did take care of the EQstream errors in both world and zone compiles, however now I get a whole slew of other errors, all dealing with WinSock2.h or WinSock.h - never had this problem before when compiling w/ VS.NET 2003, what gives? Anyone?

Regards,
SI

[Sakrateri]

by remove eqnetwork.cpp do you mean just delete the file?

[cavedude]

No, you have to remove it from the project.

[Sarepean]

Every single winsock2.h error I receive in ANY compile comes from 5 or 6 files and they all start with this "perl_". For example, "perl_client" and stuff like that.

I think I've found the reason why those error out, but I can't find a way to fix it. The devs say that it was fixed in the development branch, but even that compiles with the same errors I was getting before. =/

Here's the post (I can't find quote, otherwise I'd quote it)

-----------------------------------------------------------------

After some code inspection, I found out that both Apache-1.3.20 (os.h) and
mod_perl-1.26 (mod_perl.h) include <winsock2.h> BUT Perl-5.6.1
(/usr/perl/lib/CORE/sys/socket.h) includes <winsock.h>
As the result, compilation failed because of these 2 conflicting header file
inclusion. The include hierachy looks something like this:

Icon.h -> mod_perl.h -> winsock2.h and perl.h
perl.h -> sys/socket.h (in /perl/lib/CORE) -> winsock.h!!

In general, any mod_perl Apache modules (eg: Apache::Icon and FileMan) with C code would fail to compile due to the exact reason.

Any suggestions on how to get around this?

---------------------------------------------------------------------


None of my other files have a problem with any winsock2.h or winsock.h complications. The way I understand it is that to fix this, I would either have to #define WIN_LEAN_AND_MEAN or have the #include winsock2.h call before any calls to icon.h or perl.h

I've installed my platform SDK as recommended by another thread and that didn't do anything for my problem. =/ I'm also running the latest service pack for Visual Studio 2003 .NET Pro.

Please Advise.
-Sarepean