EQEmu DEV-C++ Howto (updated for 5.5DR1)

[Shadow-Wolf]

wouldn't know what to do about your problem mine worked fine when i used it.

[Lurker_005]

dingo01 do you have a copy of libmysql.dll somewhere in your path, or in your EQEmu dir?

Also The Dev-cpp compiled files seemed to work fine with one exception, they didn't close cleanly. World has an error about reading memory, and then the zones have to be forced to close.


And I can confirm that the perl quests work as well. See my post earlier.

[dingo01]

The only place I had libmysql.dll was in C:\mysql\bin and C:\mysql\lib\opt. I've kind of given up on it for now, though, since I just saw that the DR2 binaries were released, and those work great.

Thanks, though!

[Tertiary]

Originally Posted by Lurker_005

The Dev-cpp compiled files seemed to work fine with one exception, they didn't close cleanly. World has an error about reading memory, and then the zones have to be forced to close.

I assume you mean using 'worldshutdown' from the console, or #worldshutdown from the client ?

Does this happen all the time ? I did some tests today and worldshutdown closes the world and zone processes cleanly each time for me.

[Lurker_005]

Originally Posted by Tertiary

I assume you mean using 'worldshutdown' from the console, or #worldshutdown from the client ?

Does this happen all the time ? I did some tests today and worldshutdown closes the world and zone processes cleanly each time for me.

Actually I usually just kill the dos box
And again I am using mingw 3.3.1 not sure what differances that makes.

[diolas]

world.exe and zone.exe are now asking for libmysql.dll

I did a search on my Hd and found quite a few. I've tried a few but having been gettin strange errors regarding memory access when I attempt to close the window (the window closes after I hit ok and the new compilation seemed to work just fine). I was mainly curious as to what this bug is and if it's related to me not knowing which libmysql.dll to use.

[nascarfan1888]

how do i get reimp out of a mingw-utils-0.2.tar?????

More specifically how do i use a .tar file. Nothing i have will open the file!!

[Lurker_005]

Tar is a standard storage format for the unix (linux) OS

While there should be several utils for windows that will read it, you can get tar from http://gnuwin32.sourceforge.net/packages.html

[Muuss]

Winzip is known to be able to work with tarball files, and even with tar.gz files.

[nascarfan1888]

when compiling world.dev i have the following errors

console.cpp C:\eqemu\5.3dr3dev\world\console.cpp
In member function `void Console::ProcessCommand(const char*)':
684 C:\eqemu\5.3dr3dev\world\console.cpp
`GetOS' undeclared (first use this function)

(Each undeclared identifier is reported only once for each
687 C:\eqemu\5.3dr3dev\world\console.cpp
`Ver_name' undeclared (first use this function)
688 C:\eqemu\5.3dr3dev\world\console.cpp
`Ver_build' undeclared (first use this function)
688 C:\eqemu\5.3dr3dev\world\console.cpp
`ultoa' undeclared (first use this function)
689 C:\eqemu\5.3dr3dev\world\console.cpp
`Ver_min' undeclared (first use this function)
690 C:\eqemu\5.3dr3dev\world\console.cpp
`Ver_maj' undeclared (first use this function)
691 C:\eqemu\5.3dr3dev\world\console.cpp
`Ver_pid' undeclared (first use this function)
C:\eqemu\5.3dr3dev\world\Makefile.win
[Build Error] [console.o] Error 1

someone else had a problem similar to this and dingo01 said to ..

the makefile is looking for zlib.dll in the C:\dev-cpp\lib folder, so make sure you have a copy of it over there and you should be alright.

I did that and used the precompiled zlib.dll and it does not fix my problem.

[Tertiary]

If you can zip up your source dir and email it to me at eqemu@rama.demon.co.uk I will take a look at it and try and see where you are going wrong ... it will be quicker than trying to second guess where you (or I ) might have made a mistake.

Any further queries regarding a Dev-C++ compile should really go in Win32 server support, as it is really not an EQEmu development issue.

[Monrezz]

Great work Tertiary! Nice contribution to the community

The file sizes are huge compared to the binaries - is there any way of compressing them or optimizing them so they are smaller?

Please could one of the Dev's merge this with the CVS?

Nice work,

Monrezz

[Tertiary]

Originally Posted by monrezz

The file sizes are huge compared to the binaries - is there any way of compressing them or optimizing them so they are smaller?

The .dev files I included with my .zip have debugging information turned on for world or zone (or both). See Muuss' post earlier in this thread for how to turn this off which will make the files smaller.

[Monrezz]

What exactly does rebuild all do, compared to just compiling? I tried compiling EmuShareMem.dll and World.exe - both compiled fine without errors, and work. Not tried zone as you said it would crash/fail to compile. What does the rebuild all do...?

Turned off the debugging - thanks!

if I download the source again I assume it is going to overwrite the changes I (you) made to the files. Is there a quick way of putting it all back in, or will I just have to wait until a dev decides your code should be merged with CVS?

Monrezz

[Tertiary]

Originally Posted by monrezz

What exactly does rebuild all do, compared to just compiling?

If you just select compile, it will only re-compile source files that have changed since you last compiled everything ... normally this is what you want, since it makes recompiling quicker, i.e. if you only change one source file, only that one will be recompiled.

The problem Dev-C++ has is that common/database.cpp has an #ifdef ZONE statement which compiles extra code if you are building zone.exe.

Unfortunately Dev-C++ is not smart enough to know that it should recompile this file when you compile zone.exe ... as far as it is concerned there have been no changes to database.cpp since it last compiled it (when you built world.exe), hence you need to do a 'rebuild all' to force it to recompile database.cpp.

Hope that makes sense.

Is there a quick way of putting it all back in, or will I just have to wait until a dev decides your code should be merged with CVS?

There is a util called diff which could be used to create context diffs between the official source and the source patched to compile under Dev-C++. Then you could just apply this 'diff' using the 'patch' command when you download the latest source from CVS.

patch and diff come with MSYS (www.mingw.org) ... I just haven't been motivated enough to produce a diff, so for now, adding the changes back by hand is what you need to do.