From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: duplicate targets in Makefile rule
Date: Thu, 10 Feb 2000 14:23:11 +0000 [thread overview]
Message-ID: <20000210142311.A14018@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <000501bf73ce$4f1c3890$21c9ca95@mow.siemens.ru>
Andrej Borsenkow (Andrej.Borsenkow@mow.siemens.ru) wrote:
> Sorry? Pls, see 9543, 9687, 9593 and more in this thread.
Hmm. I did do a search on zsh-workers before I e-mailed the list
about this, but the engine came up with no matches, and for some
reason, I still can't get any query similar to
`zsh.texi;given;once;rule' to produce the relevant articles, even with
`partial match' switched on. Anyway, thanks for the pointers, and
sorry for the extra noise. Just for reference, I think you meant 9587
rather than 9687.
> The current problem is, zsh.texi should be in source dir (as it is supposed
> to exists even if user does not have yodl) - so, it belongs to src dir. The
> change you proposed make zsh.texi target name dependent on source dir
> location. So, it you want to rebuild just the texi, you'll have to know
> exact src location and type "make /path/to/source/dir/zsh.texi"
>
> For this reason I suggested having standard targets man, texi, info etc and
> make them depend on actual files. Like
>
> texi: $(sdir)/zsh.texi
>
> $(sdir)/zsh.texi: ... (as currently)
>
> Then you can just say "make texi" or "make man". Looks better to me :-)
>
> So far there was no reply.
Maybe that's because you followed your suggestion with `That's what
bash does.' ;-)
Anyway, this needs to be resolved fairly swiftly, as presumably anyone
using gmake is currently unable to build the docs. I don't know
enough about the Makefile structure in general to comment on your
suggestion, but here's another suggestion which feel free to shoot
down in flames :-) It works for when sdir is `.', but is untested
otherwise.
Index: Doc/Makefile.in
===================================================================
RCS file: /projects/zsh/zsh/Doc/Makefile.in,v
retrieving revision 1.1.1.60
diff -u -r1.1.1.60 Makefile.in
--- Doc/Makefile.in 2000/02/07 01:59:21 1.1.1.60
+++ Doc/Makefile.in 2000/02/10 14:16:11
@@ -82,7 +82,13 @@
zsh.dvi: $(sdir)/zsh.texi
$(TEXI2DVI) $(sdir)/zsh.texi
-zsh.texi $(sdir)/zsh.texi:
+ifeq ($(sdir),.)
+ ZSHTEXIS=zsh.texi
+else
+ ZSHTEXIS=zsh.texi $(sdir)/zsh.texi
+endif
+
+$(ZSHTEXIS):
case $@ in \
*/*) target=$@ ;; \
*) target=$(sdir)/$@ ;; \
next prev parent reply other threads:[~2000-02-10 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-09 23:58 Adam Spiers
2000-02-10 9:57 ` Zefram
2000-02-10 13:37 ` Adam Spiers
2000-02-10 13:54 ` Andrej Borsenkow
2000-02-10 14:23 ` Adam Spiers [this message]
2000-02-10 14:31 ` Zefram
2000-02-10 15:36 ` PATCH: " Adam Spiers
2000-02-10 15:43 ` Zefram
2000-02-10 17:03 ` Adam Spiers
2000-02-10 17:11 ` Zefram
2000-02-21 2:12 ` Adam Spiers
2000-02-21 10:07 ` Zefram
2000-02-21 10:39 ` Adam Spiers
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=20000210142311.A14018@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--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).