diff options
| author | Bruce Momjian <bruce@momjian.us> | 2004-03-09 04:53:37 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2004-03-09 04:53:37 +0000 |
| commit | 53cd7cd8a9168d4b2e2feb52129336429cc99b98 (patch) | |
| tree | f2d9dd2f786a6cdaeac1bab7dbdb5c27c447e006 /src/tutorial/funcs.c | |
| parent | f0f4e82f45462349bb30f3c4cc9792fa54525575 (diff) | |
| download | postgresql-53cd7cd8a9168d4b2e2feb52129336429cc99b98.tar.gz postgresql-53cd7cd8a9168d4b2e2feb52129336429cc99b98.zip | |
Make a separate win32 debug DLL along with the non-debug version:
Currently, src/interfaces/libpq/win32.mak builds a statically-linked
library "libpq.lib", a debug dll "libpq.dll", import library for the
debug dll "libpqdll.lib", a release dll "libpq.dll", import library for
the release dll "libpqdll.lib". To avoid naming clashes, I would make
the debug dll and import libraries "libpqd.dll" and "libpqddll.lib".
Basically, the debug build uses the cl flags: "/MDd /D _DEBUG", and the
release build uses the cl flags "/MD /D NDEBUG". Usually the debug
build has a "D" suffix on the file name, so for example:
libpqd.dll libpq, debug build
libpqd.lib libpq, debug build, import library
libpq.dll libpq, release build
libpq.lib libpq, release build, import library
David Turner
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions