#2
Posted 14 April 2011 - 04:52 PM
The first one is loaded dynamically by eduke32.debug.exe and contains some code to dump the stack to a crashlog file. The two after that are just dependencies of the first one due to some internalization functions that it uses; Helixhorned sent me a patch to stub out the code that depends on that so that we could get git of them but since I'm a lazy fuck I haven't even looked at it yet.
The fourth DLL is an alternate memory allocator called nedmalloc that EDuke32 tries to load at runtime; it's supposed to be faster than the libc one.
names.h is just a bunch of names to tile number mappings; the editor reads it for user-friendliness.
The bottomline is that none of these are strictly required, you will still be able to use EDuke32 if they're not present.
1