From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: raeburn@raeburn.org, emacs-devel@gnu.org
Subject: Re: buildobj.lst and Windows builds - a tiny bit of help needed?
Date: Sun, 23 Aug 2009 21:02:18 +0300 [thread overview]
Message-ID: <83bpm6flxx.fsf@gnu.org> (raw)
In-Reply-To: <4A917183.9090404@gnu.org>
> Date: Mon, 24 Aug 2009 00:42:43 +0800
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Emacs Developers <emacs-devel@gnu.org>
>
> Ken Raeburn wrote:
> >
> > echo $(ARGQUOTE)#define BUILDOBJ $(DQUOTE)\$(ARGQUOTE) >
> > $(SRC)/buildobj.h
> > echo $(OBJ0) $(ARGQUOTE)\$(ARGQUOTE) >> $(SRC)/buildobj.h
>
> Yes, that looks about right.
>
> > Is one backslash what I need here, if I want to get one written to the
> > file at the end of the line? Or does some backslash quote processing
> > happen, and I need two?
>
> If you don't need to double the backslashes in the main Makefile.in,
> then I don't think it will be necessary here. If you do need to double
> them in Makefile.in, then it is probably dependent on the shell in use,
> and we'll have to add some more definitions to correctly cope with the
> differences.
I think it will be hard to DTRT without shell-specific targets: a
Unixy shell needs to see the backslash escaped, the Windows shell
needs to see it alone. $(ARGQUOTE) will not help here, since with
stock Windows shell, $(ARGQUOTE)\$(ARGQUOTE) evaluates to "\", and the
backslash will escape the quote, which is not what we want.
next prev parent reply other threads:[~2009-08-23 18:02 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 [this message]
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
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=83bpm6flxx.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.