Setup private server on PCDuino
 

I try to setup EQEmu on PCDuino, most of components could be compiled successfully; however, that is a problem on

- EQEmuLoginServer

It seems that the following pre-compile libaraies do not support this platform
libEQEmuAuthCrypto.a
libcryptopp.a

Could I get the source code to try?

Thanks

P.S. system message
uname -a
Linux pc-pcduino 3.4.29+ #1 PREEMPT Fri May 3 18:56:03 CST 2013 armv7l armv7l armv7l GNU/Linux

I would just use the public login, I'm also not sure EQEmu has been tested on platforms that aren't x86 based, so it might not work well at all.

I'd guess it would probably work ok but be limited by the amount of memory available.

it is ok to limit by the amount of memory availabe, just try.

I don't think you're gonna get the encryption libraries compiled for PCDuino, just compile without the login server and use the public one. I doubt the server would work very well on the platform and might run into other issues since EQEmu was coded with x86/x86_64 in mind.

You're very focused on this, but it really shouldn't be an issue. The ARM CPU is little endian, and the platform is linux/GCC which the server already compiles on.

Quick look, you will have to do something about StackWalker being included in CMake stuff since that has inline asm, although it looks like that isn't used on non-Windows platform, but I think its still compiled (my build folder includes Its object file at least)

All of the StackWalker code is ifdef'd out on anything other than Windows.

As long as it's little endian I don't see any significant hurdles to getting it to run on a specific architecture that's running Linux. Outside having to gather up all the dependencies that is.

I've been thinking of releasing the encryption for a while, as I think the current situation is silly.

I was actually looking for this myself - I just saw this thread and it's exactly the issue I'm running into (I'm now for shits and giggles trying to get an EQEmulator server running on a NAS box, which is running wheezy. Everything goes fine until the moment the loginserver compiles, at which point the cryptopp makes it crap out).

Either the possibility to compile it for our own devices, or an ARM compiled version, would be very much appreciated.

You could just run the login server on a different box or use the public login server and keep your server locked.

While technically true that I could run the loginserver from another device, if I can have the loginserver run or compile on said other device I might as well just run both there - after all, the loginserver itself does not take up that much power for one server, and if the EQServer is down it doesn't matter if the loginserver is too.

I'm trying to get it to connect to the public login at the moment, but I'm having a segment fault in the shared memory thing - I'm gonna mess around with this some more and get back to it later.

Ideally it would be great if all the parts ran on the device, but right now they can't. It just seems that rather than let that stop you from trying to get the other 90% of the server working you just work around that small issue and move on to the rest.

Is the crash while generating the shared memory file or when it's trying to load it? How big is the file compared to the free memory on the device?

It compiled fine, but I may have a database issue that I'm trying to get to the bottom of. It seems that since a while the peqdb is no longer easily wget-able, and loading it is being awkward.

But you're right, as long as there is a workaround (there are two, actually - eqemu login or on another machine) it isn't an "urgent" issue, just something that would make it easier for me.