From: ludo@gnu.org (Ludovic Courtès)
To: "Taylan Ulrich \"Bayırlı/Kammer\"" <taylanbayirli@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] build: Fix out-of-tree building of documentation.
Date: Sat, 09 Jan 2016 22:30:57 +0100 [thread overview]
Message-ID: <87vb72784u.fsf@gnu.org> (raw)
In-Reply-To: <87fuy6ydmj.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Sat, 09 Jan 2016 16:30:12 +0100")
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> From 41650754511487f5f1f937317eebd80c19ca8bf1 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=C4=B1rl=C4=B1/Kammer?=
> <taylanbayirli@gmail.com>
> Date: Sat, 9 Jan 2016 15:56:23 +0100
> Subject: [PATCH] build: Fix out-of-tree building of documentation.
>
> * doc.am (.dot.png, .dot.pdf, .dot.eps, .png.eps): Create the directory
> for each target in case of out-of-tree building.
The files in $(DOT_VECTOR_GRAPHICS) are part of the distribution. Thus,
when building from a tarball, they are in $(srcdir), not in $(builddir).
However, when building from Git out-of-tree, they should go do $(srcdir)
as well (as is done for Info files.)
A fix would be:
[-- Attachment #2: Type: text/x-patch, Size: 830 bytes --]
diff --git a/doc.am b/doc.am
index e3a91cc..21b08be 100644
--- a/doc.am
+++ b/doc.am
@@ -1,5 +1,5 @@
# GNU Guix --- Functional package management for GNU
-# Copyright © 2012, 2013, 2014, 2015 Ludovic Courtès <ludo@gnu.org>
+# Copyright © 2012, 2013, 2014, 2015, 2016 Ludovic Courtès <ludo@gnu.org>
# Copyright © 2013 Andreas Enge <andreas@enge.fr>
#
# This file is part of GNU Guix.
@@ -66,15 +66,15 @@ DOT_OPTIONS = \
.dot.png:
$(DOT) -Tpng $(DOT_OPTIONS) < "$<" > "$@.tmp"
- mv "$@.tmp" "$@"
+ mv "$@.tmp" "$(srcdir)/$@"
.dot.pdf:
$(DOT) -Tpdf $(DOT_OPTIONS) < "$<" > "$@.tmp"
- mv "$@.tmp" "$@"
+ mv "$@.tmp" "$(srcdir)/$@"
.dot.eps:
$(DOT) -Teps $(DOT_OPTIONS) < "$<" > "$@.tmp"
- mv "$@.tmp" "$@"
+ mv "$@.tmp" "$(srcdir)/$@"
.png.eps:
convert "$<" "$@-tmp.eps"
[-- Attachment #3: Type: text/plain, Size: 37 bytes --]
Does it work for you?
Ludo’.
next prev parent reply other threads:[~2016-01-09 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 15:30 [PATCH] build: Fix out-of-tree building of documentation Taylan Ulrich Bayırlı/Kammer
2016-01-09 21:30 ` Ludovic Courtès [this message]
2016-01-10 9:49 ` Taylan Ulrich Bayırlı/Kammer
2016-01-10 10:34 ` Taylan Ulrich Bayırlı/Kammer
2016-01-10 21:03 ` Ludovic Courtès
2016-01-10 21:33 ` Taylan Ulrich Bayırlı/Kammer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb72784u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=taylanbayirli@gmail.com \
/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.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).