ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2000/07/30/17:59:18

Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3984A4FD.4B6AE90C@ece.gatech.edu>
Date: Sun, 30 Jul 2000 17:58:21 -0400
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-apps AT sourceware DOT cygnus DOT com
Subject: gdbm package available for test

gdbm is the GNU database package and is a prerequisite for cvs. This is
the initial port of gdbm to cygwin's new packaging scheme. I've had
gdbm-1.8.0 on cygutils for some time, but the cygutils version was
staticlib only, and didn't follow the package layout rules established
here on cygwin-apps. The package also includes several test utilities
and compatibility headers, so that gdbm can be used as a drop-in
replacement for ndbm and dbm. The binary package includes dynamically
linked versions of these test programs, although the build process will
make both dynamically and statically linked versions.

The package is now available for testing at


Building requires gcc-2.95.2-2 and binutils-20000722-1 or later.


o import-lib libfoo.dll.a
o stripped dll libfoo.dll
o static-lib libfoo.a
o cygwin-specific doc /usr/doc/Cygwin/gdbm-1.8.0.README
o generic docs in /usr/doc/gdbm-1.8.0/*
o source archive already has the cygwin-specific patch applied

o cygwin-specific README and PATCH are stored in the source archive,
under <top>/CYGWIN-PATCHES/* (although the patch has already been
applied to the archive itself).

o define -DGDBM_STATIC to get the 'correct' #define's when compiling a
.o that will be linked statically -- as well as using 'gcc -static'
during the link step

o also use -DGDBM_STATIC when using the compatibility headers for ndbm
and dbm, if linking statically.

o no special -Ddefine options needed (or link options) needed to link to
the dll, whether using 'gdbm.h' or the ndbm/dbm compatibility headers

Comments and test reports welcome!


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019