From 067d6d8e834db3159981894a8fdfdbea6657c096 Mon Sep 17 00:00:00 2001 From: Andy McFadden Date: Sun, 9 Feb 2003 01:41:41 +0000 Subject: [PATCH] Removed remarks about what hoops to jump through when linking against NufxLib as a DLL. --- nufxlib-0/README.txt | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/nufxlib-0/README.txt b/nufxlib-0/README.txt index 525188b..c24a76e 100644 --- a/nufxlib-0/README.txt +++ b/nufxlib-0/README.txt @@ -86,21 +86,6 @@ When it finishes, run "test-basic.exe". If you want to build NufxLib as a DLL, use "makefile.dll" instead. If you're using zlib or libbz2, these will need to be linked into the DLL. -You will probably need to set the application that links against it to -use the "multithreaded DLL" version of the C library. (In Visual C++, -go to Project->Settings...->C/C++ tab, select Category: Code Generation, -and in the "Use run-time library" box choose "Multithreaded DLL" for -Release and "Debug Multithreaded DLL" for Debug.) - -You have to use the DLL version because NufxLib allows certain calls to -pass in a malloc()ed pointer which the library then takes ownership of. -If nufxlib.dll and the application are using different heaps, the memory -is being allocated on one and freed from another, which doesn't work. -Debug versions of the DLL will halt with an assertion failure, most -likely in a NuFlush or NuClose call. Non-debug versions will silently -leak memory, or possibly corrupt other structures. You can test this -easily by running the "test-basic" application after linking it against -the DLL without specifying "DLL=1" on the makefile line. Other Notes