* Jose-Marcio wrote on Mon, Jul 28, 2008 at 05:27:00PM CEST:
>
> In fact, the real reason, for me, to have another target, is to reuse
> some configuration values defined during "configure" run, such as
> prefix, all dirs (sysconfdir, datadir, sbindir, ... ). Maybe it could be
> interesting t
Hello Ralf,
On 7/28/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > #When src/foo.c is newer than src/foo,
> > #GNU make applies it's implicit rule, like this:
> > # gcc -g -O2../ns/src/foo.c -o src/foo
>
> Yep. Kinda ugly. You should be able to work around it by adding
> an empty rule:
Hi Karl,
* Karl Berry wrote on Tue, Jul 29, 2008 at 12:30:52AM CEST:
> > 1) do you have any interest in eliminating the dependency on ncftpput?
>
> Sure.
>
> So perhaps the best outcome would be for gnupload to use ftp itself,
> instead of ncftpput? Ie, this stuff could become a functio
> 1) do you have any interest in eliminating the dependency on ncftpput?
Sure.
So perhaps the best outcome would be for gnupload to use ftp itself,
instead of ncftpput? Ie, this stuff could become a function in
gnupload?
Failing that, perhaps gnupload could use a variable, e.g.,
: ${FTP
Hello Ineiev,
* Ineiev wrote on Mon, Jul 28, 2008 at 11:08:20AM CEST:
> dist_bin_SCRIPTS=src/foo
> bin_PROGRAMS=bar
> bar_SOURCES=src/bar.c src/foo.c
> #When src/foo.c is newer than src/foo,
> #GNU make applies it's implicit rule, like this:
> # gcc -g -O2../ns/src/foo.c -o src/foo
Yep. Ki
Monty Taylor <[EMAIL PROTECTED]> writes:
> I've got a project that has 24 Makefile.am files. At the top of all of
> them at the moment, I've got:
>
> AM_CPPFLAGS = -I$(top_builddir)/include -I$(top_srcdir)/include
I tend to write "include $(top_srcdir)/Make.vars" at the top of
each Makefile.am, a
Hello Ralf,
Ralf Wildenhues wrote:
* Jose-Marcio wrote on Mon, Jul 21, 2008 at 04:46:29PM CEST:
Well, one reason I'm hesitant is that I think most such pre- or post-
actions are pretty system-dependent, more so than other tasks routinely
done in makefiles. For example, they would often dep
