zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
	"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: RE: Makefile target given more than once (Re: 3.1.6-dev-17)
Date: Mon, 7 Feb 2000 12:56:13 +0300	[thread overview]
Message-ID: <NCBBLINKDKKLMKDJFLMCMEIJCBAA.Andrej.Borsenkow@mow.siemens.ru> (raw)
In-Reply-To: <1000207080634.ZM8445@candle.brasslantern.com>

> } > Hrm.  This would appear to be gmake cleverly discovering that
> when $(sdir)
> } > is ".", zsh.texi and $(sdir)/zsh.texi are the same target.
> }
> } So far it is just noise. But why we need two targets? One is obviously
> } redundant.
>
> No, that's not true.
>
> The $(sdir)/zsh.texi target is used in dependencies elsewhere in the
> Makefile.
>
> The zsh.texi target is for (cd Doc; make zsh.texi) which is executed by
> the top-level Makefile and also may be typed by a user.
>

Here I'm confused. Top-level Makefile never does (cd Doc; make zsh.texi); it
does all, install, clean ... but never subdir-specific targets.

So, we need zsh.texi in source dir to include it with distribution (for
users without yodl). Right?

I suggest to use placeholder like texi, dvi, html etc as main targets and
make them depend on actual files. Like

all: man texi

man: $(MAN)

texi: $(sdir)/zsh.texi

That is what e.g. bash does.

/andrej


      reply	other threads:[~2000-02-07  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-02 21:16 3.1.6-dev-17 Peter Stephenson
2000-02-03 10:11 ` 3.1.6-dev-17 Andrej Borsenkow
2000-02-06 19:15   ` Makefile target given more than once (Re: 3.1.6-dev-17) Bart Schaefer
2000-02-07  7:34     ` Andrej Borsenkow
2000-02-07  8:06       ` Bart Schaefer
2000-02-07  9:56         ` Andrej Borsenkow [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NCBBLINKDKKLMKDJFLMCMEIJCBAA.Andrej.Borsenkow@mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).