Looking for a solution to this DR1 problem...

Sarepean · #1 05-05-2005, 10:29 AM

Thanks. I was about to head out the door, but I'll get to tinkering with all of this as soon as I get back. =)

**cavedude** · #2 05-05-2005, 10:42 AM

I had that same problem when dynamic opcodes first hit CVS for 6.0DR3. My solution was and still is to use .NET 2003 to compile. For whatever reason VS 6.0 compiles always give me that error. Also, .NET compiles the release source flawlessly out of the box so to say without having to editing the projects. (Perl compile fails with the same errors as VS 6.0)

RangerDown · #3 05-05-2005, 10:57 AM

FYI, all official Windows compiles use VS .NET (2k3 I believe) just as you do. If you are still using VS 6.0, you might want to consider compiling with .NET 2k3 -- as of last I heard, this is what the devs consider "official" and they probably won't go out of their way to keep backward compatibility with older Visual Studio versions.

mystic414 · #4 05-05-2005, 02:29 PM

I had that exact problem.

You need to add a bunch of files to the sharemem and world projects. Look in the common directory and add common headers/source files like emu_opcodes.h/.cpp emu_oplist, eq_opcodes, opcodemgr... basically everything with "opcode" in it. Recompile and it should work fine.

sonicintuition · #5 05-06-2005, 12:10 AM

Thanks guys. Actually I do use VS.NET 2003 ..always have.

I'll recompile it later with your tip Mystic. Would be cool if it works. thanks again!

Regards,
SI

**cavedude** · #6 05-06-2005, 12:24 AM

Re-download the source and use the server.sln to compile file NOT the dsw file. It will work perfectly without having to change a thing.

sonicintuition · #7 05-06-2005, 03:21 AM

Hey, thanks cavedude. I had tried opening the .sln file in vs.net prior to this issue but always got an error message and just assumed it didn't work because of it. Just goes to show that one should never assume. Thanks again, I really appreciate it!

Regards,
SI