> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Simon" == Simon Perkins <[EMAIL PROTECTED]> writes:
Simon> I also notice that automake generates an 'installcheck' target,
Simon> but it's not described in the documentation.
Tom> Automake's user docs are nonexistent :-(. This is desc
On Sun, Dec 30, 2001 at 06:40:22PM -0700, Tom Tromey wrote:
> > "Ryan" == Ryan T Sammartino <[EMAIL PROTECTED]> writes:
> Ryan> With MS VCrap++, if you use the /Gm, /Gi or /ZI options, it uses
>
> What do these options do?
/Gm = enable minimal rebuild
/Gi = can't remember off-hand
/ZI = enab
ss multiple
+ paragraphs. This fixes a very nasty bug reported by Dmitry Mikhin
+ where only the first paragraph of such a multi-paragraph rule was
+ discarded, but leaves many latent bugs (see the FIXMEs).
+
Index: automake.in
=====
hi
i'm working on porting a project that build multiple libraries and multiple
executables. what i would like to happen after i run 'make' in the top
level directory is that all the built libraries will be in $(top_srcdir)/lib
instead of their respective build directories.
ideally ar should c
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Tom> Automake's user docs are nonexistent :-(. This is described in
Tom> the GNU Coding Standards. Really it would be nice if we had a
Tom> separate document that explained the standard targets to the
Tom> user. People could distribute
> "Patrick" == Dahiroc, Patrick <[EMAIL PROTECTED]> writes:
Patrick> ideally ar should create the libraries in $(top_srcdir)/lib
Patrick> with the command: ar cru $(top_srcdir)/lib/mylib.a A.o B.o
Patrick> C.o. is there way to make automake behave like this?
Putting any built object into sr
