Is EqEmu 32 or 64 bit?

[chaple2008]

I'm trying to set up a development environment to help out, I'm not really a newb, been coding for a while.

The documentation could be slightly better :) I've gotten cmake to work it build the files. Now I've seen some folders that said x64 in them for dependencies and just want to make sure that this is a 32 bit application.

Also, I'm getting an invalid or corrupt file: cannot read at 0x2F8 in libsodium.dll when I compile during linking. Any ideas?

[chaple2008]

Well, I tried compiling the libsodium library from a the website and got the same error.. I must have something f'd up.

[Nightrider84]

Generally its less buggy when you compile in 32bit I don't recommend 64

[superpally1]

https://github.com/EQEmu/Server/wiki/Ground-Up-Windows-Install

64 bit, no issues I've noticed.

[prestanneth]

Make sure your make file SODIUM_LIBRARIES setting is linked against libsodium.lib and not the dll itself that's usually what causes the corrupt/ cant read errors.

we've been using x64 for years over the x32 compile, but comes down to personal preference/ familiarity. x64 works just fine, has for a long time.
Most OS are 64 bit these days, so seems more logical to start targeting it even though there is no real difference in terms of eqemu.

[Uleat]

Actually..many software developers still use 32-bit builds to save memory.

There aren't a lot of things out there that require more than 4 GB of addressable ram.

You can take code (such as EQEmu) and compile both versions of it.

the 64-bit will always have a larger footprint if for no other reason than the size of pointers.

Pointers are 4-bytes in 32-bit builds and 8-bytes in 64-bit builds.

There may be some small gain in performance by using 64-bit pointers due to using 'native size' ..
but, the real difference between size and performance is likely negligible and it really boils down to choice.