unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: buildobj.lst and Windows builds - a tiny bit of help needed?
Date: Sun, 23 Aug 2009 06:48:58 -0400	[thread overview]
Message-ID: <72B7514B-A488-4FA1-A0C6-8114E60E9209@raeburn.org> (raw)
In-Reply-To: <4A90FE29.9080205@gnu.org>

On Aug 23, 2009, at 04:30, Jason Rumney wrote:
> Ken Raeburn wrote:
>> I think it should be pretty straightforward, as you can see from  
>> the changes in the attached diff, but it does involve make commands  
>> that have to write double-quotes and backslashes to files (and thus  
>> get the quoting right), and an object file list that is supposedly  
>> too long to process on one command line...
> To deal with quoting correctly for all variants of make/shell there  
> are macros ARGQUOTE and DQUOTE.

Ah...  I saw them, but didn't see very good examples until I looked  
more closely at some of the other (lisp, leim) makefile.w32-in files.   
So it looks like I should write the rules something like this?

	echo $(ARGQUOTE)#define BUILDOBJ $(DQUOTE)\$(ARGQUOTE)  > $(SRC)/ 
buildobj.h
	echo $(OBJ0)     $(ARGQUOTE)\$(ARGQUOTE) >> $(SRC)/buildobj.h

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?

Thanks!

Ken




  reply	other threads:[~2009-08-23 10:48 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 [this message]
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

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72B7514B-A488-4FA1-A0C6-8114E60E9209@raeburn.org \
    --to=raeburn@raeburn.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).