New CVS dump Windows compile issues

[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

[cavedude]

WARNING: This is a rough hack so I take no responsiblity for what it may do to your system.

This is how I got zone with perl support to compile on my Windows XP/Visual Studio .Net 2003 system. I went in-game and did a fairly thorough check of standard game functions, perl functions, and server stability/speed and everything seemed alright.

First, edit C:\Perl\lib\CORE\sys\socket.h

Change the winsock.h include line to winsock2.h

Finally add this to perlparser.cpp right below the features.h include line:

#define WIN32_LEAN_AND_MEAN
#ifdef __GNUC__
#  define Win32_Winsock
#endif

After it compiles you may wanna change socket.h back to normal, especially if you do other work with the perl source.

[Sakrateri]

Im new to compiling , how would I go about removing it from the project ? or is that to complicated to explain here? anyways thanks for the reply