Message-Id: <199903040728.CAA24367@delorie.com>
From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization: none provided
To: djgpp AT delorie DOT com
Date: Thu, 4 Mar 1999 08:30:36 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Rhide Compiling Prob
References: <rbaD2.2612$G26 DOT 221 AT tundra DOT ops DOT attcanada DOT net>
In-reply-to: <Pine.SUN.3.91.990303164731.11520C-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp AT delorie DOT com

> Are you sure?  If I understand you correctly, you are describing a bug in 
> RHIDE whereby file names with embedded spaces aren't supported.  Since 

Exactly.

> DJGPP's version of library function `system' does support quoted file 
> names with embedded whitespace, I wonder why RHIDE cannot.

This is, because RHIDE uses some special techniques to
generate the commandline. Internally it works similar to the
rules used by a Makefile. It takes originally one variable (let's
say $(RHIDE_COMPILE.c.o)) and expands this until there are
no other tokens in it to be expanded. I know, that DJGPP's 
system() can handle quoted strings, but with RHIDE it is the same
like with GNU Make, or can you tell me an easy way to tell
GNU Make how to handle the filename in the Makefile below
correct?

sources='this is a file.c' other.c
objects=$(patsubst %.c,%.o,$(sources))

test: $(objects)



******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************