This builds a debug version of the DLL's along with the non-debug version. Patch applied. Thanks.
--------------------------------------------------------------------------- David Turner wrote: > Hi > > > > 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 > > > > > > > What do we do now? Build just one file, a lib? > > > 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". > > Attached is src/interfaces/libpq/win32.mak, modified as I described. I > also had to make a copy of libpqdll.def to change the LIBRARY directive. > > > Regards > David Turner Content-Description: libpqddll.def [ Attachment, skipping... ] Content-Description: win32.mak [ Attachment, skipping... ] -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
