On Tue, 20 Dec 2005, D.J. Heap wrote:
> On 12/19/05, Daniel Rall <firstname.lastname@example.org> wrote:
> > On Sat, 17 Dec 2005, email@example.com wrote:
> > ...
> > > Log:
> > > * build.conf: Add svnsync to __ALL__ so it gets built for tests.
> > ...
> > > --- trunk/build.conf (original)
> > > +++ trunk/build.conf Sat Dec 17 22:13:17 2005
> > > @@ -823,7 +823,7 @@
> > > type = project
> > > path = build/win32
> > > libs = svn svnserve svnadmin svnlook svnversion svndumpfilter
> > > - mod_authz_svn mod_dav_svn
> > > + mod_authz_svn mod_dav_svn svnsync
> > Any reason why that config section field is named "libs" instead of
> > "deps" (or something else which isn't library-specific)?
> Not to my knowledge. "deps" makes sense to me.
While I was looking into what would need to change the field name, I
came across the section name descriptors in gen_base.py:
# Compute intra-library dependencies
for section in self.sections.values():
dependencies = (( DT_LINK, section.options.get('libs', "") ),
( DT_NONLIB, section.options.get('nonlibs', "") ),
( DT_SOURCELIB, section.options.get('sourcelibs', "")))
# dependency types
dep_types = [
'DT_INSTALL', # install areas. e.g. 'lib', 'base-lib'
'DT_OBJECT', # an object filename, depending upon .c filenames
'DT_SWIG_C', # a swig-generated .c file, depending upon .i filename(s)
'DT_LINK', # a libtool-linked filename, depending upon object fnames
'DT_NONLIB', # filename depends on object fnames, but isn't linked to them
'DT_SOURCELIB',# sources of dependency are directly compiled into target
The config section field name 'libs' still seems weird to me when used
for binaries like 'svnsync' (in the [__ALL__] section). Should that
instance be using the field name 'nonlibs' instead? Or is 'libs'
appropriate, and the name just not descriptive enough?
Received on Sun Dec 25 03:42:04 2005
- application/pgp-signature attachment: stored