Hello,
On Wed, Jan 04, 2006 at 10:49:16AM -0600, Bob Friesenhahn wrote:
> It must be nice to have such a simple project. :-)
>
> For my own project, released autoconf and automake have been fine, but
> released libtool has never been quite good enough. So for many years,
> I have used hand-twe
On Wed, 4 Jan 2006, Stepan Kasal wrote:
On Sat, Dec 24, 2005 at 10:26:10AM -0600, Bob Friesenhahn wrote:
In some cases most of the project developers don't want to have
anything to do with build maintenance. They just want to edit
existing C/C++ source code.
This is natural. But they might
Ah, my bad!
I was confused again by my own project where I have a
"maintainerclean" script that does a 'make maintainer-clean' followed by
removal of other maintainer files -- more than just maintainer-clean.
(Duh!) It looks something like this:
-8<
Hello,
On Sat, Dec 24, 2005 at 03:13:41AM -0500, David Fang wrote:
> > > [...] how do I completely clean all generated files?
> There's a target called 'maintainer-clean' that will remove them.
> This target, however, is enabled by AM_MAINTAINER_MODE, [...]
two mistakes here:
"make maintainer-c
Hello,
On Sat, Dec 24, 2005 at 08:52:12AM -0700, Ed Hartnett wrote:
> I have a project with several developers, and we keep the configure.ac
> and the configure checked in, but we are moving towards only having
> configure.ac checked in.
>
> In general there will be on developer taking the lead o
David Fang <[EMAIL PROTECTED]> writes:
>> > Interesting thought: Wouldn't it get annoying if many devs are working
>> > on one CVS controlled project, and they have different version
>> > autotools, surely each time they commit their changes they're possibly
>> > going to have conflicts? Which wou
The problem with keeping the generated files in the code management
system is that the timestamps mess up you can have a bigger mess to
clean up.
You should also knmow what versions of the auto* tools you require, and
use AC_PREREQ() in configure.ac and AUTOMAKE_OPTIONS in your Makefile.am
files.
On Saturday 24 December 2005 10:15 am, Daniel Pekelharing wrote:
> On Sat, 2005-12-24 at 09:24 +0100, Baurzhan Ismagulov wrote:
> > Hello Daniel,
> >
> > On Sat, Dec 24, 2005 at 09:40:52AM +0200, Daniel Pekelharing wrote:
> > > I am in the process of importing my project into CVS,
> > > but I am a
> > Interesting thought: Wouldn't it get annoying if many devs are working
> > on one CVS controlled project, and they have different version
> > autotools, surely each time they commit their changes they're possibly
> > going to have conflicts? Which would make the files unusable? (until
> > resol
On Sat, 24 Dec 2005, Daniel Pekelharing wrote:
Interesting thought: Wouldn't it get annoying if many devs are working
on one CVS controlled project, and they have different version
autotools, surely each time they commit their changes they're possibly
going to have conflicts? Which would make th
Daniel Pekelharing <[EMAIL PROTECTED]> writes:
> On Sat, 2005-12-24 at 09:24 +0100, Baurzhan Ismagulov wrote:
> I did think about that..
>
> But as I plan on periodically making releases, which will include all
> auto generated files, that should be OK for end users.. (I think ;-))
>
> Interesting
On Sat, 2005-12-24 at 09:24 +0100, Baurzhan Ismagulov wrote:
> Hello Daniel,
>
> On Sat, Dec 24, 2005 at 09:40:52AM +0200, Daniel Pekelharing wrote:
> > I am in the process of importing my project into CVS,
> > but I am a little confused as to Autoconf, should I import all generated
> > Makefile's
On Sat, 2005-12-24 at 03:13 -0500, David Fang wrote:
> > > Forgive a newbie question, how do I completely clean all generated
> > > files? - Apart from doing it manually? I tried "make distclean" but it's
> > > still leaving some auto generated stuff lying around.
> >
> > I don't know the answer to
Hello Daniel,
On Sat, Dec 24, 2005 at 09:40:52AM +0200, Daniel Pekelharing wrote:
> I am in the process of importing my project into CVS,
> but I am a little confused as to Autoconf, should I import all generated
> Makefile's, Makefile.in's, configure etc. ?
> I personally think I should leave the
> > Forgive a newbie question, how do I completely clean all generated
> > files? - Apart from doing it manually? I tried "make distclean" but it's
> > still leaving some auto generated stuff lying around.
>
> I don't know the answer to that. Generally it's not something you *need*
> to do; though
On Sat, 2005-12-24 at 02:56 -0500, Braden McDaniel wrote:
> On Sat, 2005-12-24 at 09:40 +0200, Daniel Pekelharing wrote:
> > Hi all,
> >
> > I am in the process of importing my project into CVS,
> > but I am a little confused as to Autoconf, should I import all generated
> > Makefile's, Makefile.i
On Sat, 2005-12-24 at 09:40 +0200, Daniel Pekelharing wrote:
> Hi all,
>
> I am in the process of importing my project into CVS,
> but I am a little confused as to Autoconf, should I import all generated
> Makefile's, Makefile.in's, configure etc. ?
> I personally think I should leave them out of
17 matches
Mail list logo
