Apple-2-Tools
/
nulib2
mirror of https://github.com/fadden/nulib2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Removed remarks about what hoops to jump through when linking against 

NufxLib as a DLL.
This commit is contained in:
Andy McFadden 2003-02-09 01:41:41 +00:00
parent 9a255d521e
commit 067d6d8e83
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
nufxlib-0/README.txt
View File

@ -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