From: James Crook <crookj@in...> - 2007-12-16 11:07:26
I noticed you recently added this 'libs' directory to CVS.
Could you say what it is for please?
I'm asking partly from a concern that it might be intended for binary
files. In more than one workplace I've seen CVS/VSS being got into a
tangle by having both source and derived binary files checked in ('to
save people time') and it ending up costing a good deal of time because
of the source files and derived files, both of which were checked in,
then getting out of sync. It's not that binary/derived files should
never ever be checked in, rather that it's if they are one needs to be
ultra careful around them and document what's been done. I'd imagine
it's not this at all - and there are no files checked in there yet. I'm
just asking to find out more.
From: Richard Ash <richard@au...> - 2007-12-16 14:01:47
On Sun, 2007-12-16 at 11:10 +0000, James Crook wrote:
> Hi Richard,
> I noticed you recently added this 'libs' directory to CVS.
> Could you say what it is for please?
To avoid a build error. Libtool tries to keep object files in
lib/.libs/. The configure script / makefile attempts to create
the .libs/ directory, but is assumes that libs/ exists, and if it
doesn't, the compile exits on an error and you can't build audacity. To
avoid this causing a load of hassle I want a clean CVS checkout to start
off with an empty libs directory so that it builds first time. It might
be more elegant to patch the build system, but I'm trying to avoid doing
too many of those at a time.
> I'm asking partly from a concern that it might be intended for binary
Well it is, but not to check them in, just to hold them when builds are
done. I should probably set CVS up to ignore all files and folders in
there, except I'm not quite sure how to do so.
Get latest updates about Open Source Projects, Conferences and News.