Hello!
I want to build Crystal Space with DLLs for the sake of easier updating of the final result. But when I tried a testing application on another computer, i found out that simply copying of crystalspace-2.0-vc100.dll into the directory of the executable doesn't work. Basically the application needs crystalspace-2.0-vc100.dll, libz-cs.dll, engine.dll, and vfs.dll but it also needs the DLLs of all plugins used.
Is there somehow a way to avoid a DLL nest like this (except static linking)? Otherwise the configurations ReleaseWithDlls/DebugWithDlls would be pretty pointless and updating an app would be heck of a work.

Thanks in advance,
aVoX.

Hello.
I am new to this engine, so I wanted to giveit a try. I set everything up as described here (even though I have VS10).
When I run the app in debug configuration, everything works perfectly, but when I switch to 'release' and want to run it, it just crashes.
Some info I can give you:

• Crystal Space 2.0 Beta 3
• Debugger report: Unhandled exception at 0x77c315de in CrystalSpaceTest1.exe: 0xC0000005: Access violation reading location 0x00000018.
• Crashes in: winsyspath.cpp, line 84

Code:

return (wcscmp (path1W, path2W) == 0);

EDIT: Additional Info:

• Version of winlibs package: The one that comes with the big lib compilation
• Operating system: Windows 7 Home Premium x86-64 (building an 32 bit application)
• Compiler: MSVCPP, that one that comes with VS10
• Video card: Nvidia GeForce GT555M
• Driver: Latest Nvidia driver (v285.62)

Thanks in advance,
aVoX

EDIT2: When I use a multi-byte charset instead of unicode, it works.