Le Vendredi 03 Juin 2005 06:17, Mark Wedel a écrit : >tchize wrote: >> Speaking about automake. >> >> Since a few week i noticed each time i do a commit, all the Makefile.in >> are commited along. Did someone change the configure script to regenerate >> automake.in file each time a ./configure is run? If that's the case, maybe >> removing Makefile.in files from cvs would be a good think (if they became >> machine dependent, there is no reason to keep them in CVS) > > Some file is out of sync, so it keeps re-running automake. One would > normally thing this should correct itself once the up to date ones are > committed. Maybe something that the makefiles depend on was committed with > a bogus date. > > The rationale for having the Makefile.in's in CVS is to make it easier for >users to grab snapshots and not need a large set of tools. Ideally, this >dependency should get fixed up somehow so that it doesn't re-run automake > every time. > >
Problem is, when i only modify some .c files, MAkefile.in's are regenerated (and commited along) >_______________________________________________ >crossfire mailing list >crossfire@metalforge.org >http://mailman.metalforge.org/mailman/listinfo/crossfire -- -- Tchize (David Delbecq) [EMAIL PROTECTED] Public PGP KEY FINGERPRINT: F4BC EF69 54CC F2B5 4621 8DAF 1C71 8E6B 5436 C17C Public PGP KEY location: http://wwwkeys.pgp.net/pgpnet/wwwkeys.html
pgpoZrkoqFAIj.pgp
Description: PGP signature
_______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
