From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: buildobj.lst and Windows builds - a tiny bit of help needed?
Date: Mon, 24 Aug 2009 21:22:04 +0300 [thread overview]
Message-ID: <83my5pdqcz.fsf@gnu.org> (raw)
In-Reply-To: <07899DEE-B1AB-4ABC-A69B-E7E78A6441EB@raeburn.org>
> From: Ken Raeburn <raeburn@raeburn.org>
> Date: Mon, 24 Aug 2009 00:16:43 -0400
> Cc: jasonr@gnu.org, emacs-devel@gnu.org
>
> Then, I think this should do it... does it look right to you?
>
> $(SRC)/buildobj.h: make-buildobj-$(SHELLTYPE)
> make-buildobj-CMD: Makefile
> echo #define BUILDOBJ "\ > $(SRC)/buildobj.h
> echo $(OBJ0) \ >> $(SRC)/buildobj.h
> echo $(OBJ1) \ >> $(SRC)/buildobj.h
> echo $(WIN32OBJ) \ >> $(SRC)/buildobj.h
> echo $(FONTOBJ) \ >> $(SRC)/buildobj.h
> echo " >> $(SRC)/buildobj.h
The first and the last lines still don't work, because `echo' retains
the quotes, but still disables the special meaning of > and >> inside
quotes, and so redirection doesn't work. I see no choice but to use
`^' to escape the quotes:
$(SRC)/buildobj.h: Makefile
echo #define BUILDOBJ ^"\ > $(SRC)/buildobj.h
echo $(OBJ0) \ >> $(SRC)/buildobj.h
echo $(OBJ1) \ >> $(SRC)/buildobj.h
echo $(WIN32OBJ) \ >> $(SRC)/buildobj.h
echo $(FONTOBJ) \ >> $(SRC)/buildobj.h
echo ^" >> $(SRC)/buildobj.h
(`^' is the CMD escape character, but only CMD supports it, Windows
programs do not, in general. Sigh.)
next prev parent reply other threads:[~2009-08-24 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 7:50 buildobj.lst and Windows builds - a tiny bit of help needed? Ken Raeburn
2009-08-23 8:30 ` Jason Rumney
2009-08-23 10:48 ` Ken Raeburn
2009-08-23 16:42 ` Jason Rumney
2009-08-23 18:02 ` Eli Zaretskii
2009-08-23 18:43 ` Ken Raeburn
2009-08-23 20:17 ` Eli Zaretskii
2009-08-23 21:07 ` Ken Raeburn
2009-08-24 3:19 ` Eli Zaretskii
2009-08-24 4:16 ` Ken Raeburn
2009-08-24 18:22 ` Eli Zaretskii [this message]
2009-08-26 7:08 ` Ken Raeburn
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=83my5pdqcz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=raeburn@raeburn.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.