all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: buildobj.lst and Windows builds - a tiny bit of help needed?
Date: Wed, 26 Aug 2009 03:08:39 -0400	[thread overview]
Message-ID: <A11658BC-1A4F-4A47-B638-072F5A949D31@raeburn.org> (raw)
In-Reply-To: <83my5pdqcz.fsf@gnu.org>

On Aug 24, 2009, at 14:22, Eli Zaretskii wrote:
> 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:

Ah, another bit of CMD syntax I wasn't familiar with.  Thanks!

> $(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

This looks like just what I need, thanks.  With this, I think I can  
make the CANNOT_DUMP build cleanly load its documentation, without  
breaking the Windows build.

Ken




      reply	other threads:[~2009-08-26  7:08 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
2009-08-26  7:08                     ` Ken Raeburn [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=A11658BC-1A4F-4A47-B638-072F5A949D31@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.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.