pgsql-server/src/interfaces/libpq win32.mak li ...

From: momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server/src/interfaces/libpq win32.mak li ...
Date: 2004-03-09 04:53:37
Message-ID: 20040309045337.BFE1AD1D9E6@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: momjian(at)svr1(dot)postgresql(dot)org 04/03/09 00:53:37

Modified files:
src/interfaces/libpq: win32.mak
Added files:
src/interfaces/libpq: libpqddll.def

Log message:
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

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2004-03-09 05:05:41 pgsql-server/ oc/src/sgml/keywords.sgml oc/src ...
Previous Message Bruce Momjian 2004-03-09 04:49:03 pgsql-server/src bin/initdb/initdb.c include/p ...