From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.devel Subject: Re: buildobj.lst and Windows builds - a tiny bit of help needed? Date: Sun, 23 Aug 2009 14:43:04 -0400 Message-ID: References: <4CC1CF5E-088F-459E-BCF7-61DEFA747DE1@raeburn.org> <4A90FE29.9080205@gnu.org> <72B7514B-A488-4FA1-A0C6-8114E60E9209@raeburn.org> <4A917183.9090404@gnu.org> <83bpm6flxx.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1251053152 18170 80.91.229.12 (23 Aug 2009 18:45:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Aug 2009 18:45:52 +0000 (UTC) Cc: emacs-devel@gnu.org, Jason Rumney To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 23 20:45:45 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MfI4T-0000d1-12 for ged-emacs-devel@m.gmane.org; Sun, 23 Aug 2009 20:45:41 +0200 Original-Received: from localhost ([127.0.0.1]:39059 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfI4S-0001WM-Cn for ged-emacs-devel@m.gmane.org; Sun, 23 Aug 2009 14:45:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfI2H-0007Lf-FL for emacs-devel@gnu.org; Sun, 23 Aug 2009 14:43:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfI2A-0007F6-HC for emacs-devel@gnu.org; Sun, 23 Aug 2009 14:43:22 -0400 Original-Received: from [199.232.76.173] (port=43976 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfI29-0007Eh-Om for emacs-devel@gnu.org; Sun, 23 Aug 2009 14:43:17 -0400 Original-Received: from splat.raeburn.org ([69.25.196.39]:51216 helo=raeburn.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MfI1y-0003jB-7e; Sun, 23 Aug 2009 14:43:14 -0400 Original-Received: from [10.0.0.172] (squish.raeburn.org [10.0.0.172]) by raeburn.org (8.14.3/8.14.1) with ESMTP id n7NIh44x000504; Sun, 23 Aug 2009 14:43:04 -0400 (EDT) In-Reply-To: <83bpm6flxx.fsf@gnu.org> X-Mailer: Apple Mail (2.936) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:114535 Archived-At: On Aug 23, 2009, at 14:02, Eli Zaretskii wrote: > 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. Ugh. Well, there already seems to be some shell-specific coding in nmake.defs and gmake.defs, so perhaps I can define $(BACKSLASH) to expand to whatever is needed for a backslash inside $(ARGQUOTE), namely two backslashes for sh and one for Windows? Though, in order to get the backslash by itself, I'd need to avoid "\" acting as a line continuation character for make. Does that mean I need to double them, or add just one more, or...? The other possibility that occurred to me was using multiple macros and string literal concatenation: echo $(ARGQUOTE)#define BUILDOBJ0 $(DQUOTE)$(OBJ0)$(DQUOTE)$ (ARGQUOTE) > $(SRC)/buildobj.h ... echo $(ARGQUOTE)#define BUILDOBJ BUILDOBJ0 BUILDOBJ1 BUILDOBJWIN32 BUILDOBJFONT$(ARGQUOTE) >> $(SRC)/buildobj.h If all the compilers available for Windows (and useable for building Emacs) support this, it may be simpler than figuring out the backslash quoting issues. Ken