From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Date: Fri, 21 Apr 2006 08:02:47 -0400
Subject: [U-Boot-Users] How can a file in directory "u-boot-1.1.4\include\configs"
 be included?
In-Reply-To: <20060420220951.907F5353A57@atlas.denx.de>
References: <20060420220951.907F5353A57@atlas.denx.de>
Message-ID: <4448C9E7.7070104@smiths-aerospace.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:
> In message <200604200844.k3K8i3wk016937@scut.edu.cn> you wrote:
>> I'm a beginner at u-boot porting and have a question about how can
>> a file in directory "u-boot-1.1.4\include\configs", say pxa255_idp.h,
> 
> There is no such file.  Both  '\i'  and  '\c'  are  undefined  escape
> sequences in the C programming language.

Hi Wolfgang,

The context here could be either cpp or shell.  Backslash \ is a valid 
escape in all shells that are worthy of being used at denx.de (I forgot 
if you prefer bash or csh).  Either way, your statement is still 
correct, there is no file "u-boot-1.1.4includeconfigs" (or 
"u-boot-1.1.4includeconfigspxa255_idp.h" to extrapolate the question).

$ ls -l u-boot-1.1.4\include\configs\pxa255_idp.h
/bin/ls: u-boot-1.1.4includeconfigspxa255_idp.h: No such file or directory

$ touch u-boot-1.1.4\include\configs\pxa255_idp.h

$ ls u-boot-1.1.4\include\configs\pxa255_idp.h
u-boot-1.1.4includeconfigspxa255_idp.h

$ cat x.c
/*
  * Test escaping in the C compiler
  */
#include "u-boot-1.1.4\include\configs\pxa255_idp.h"

int main(int argc, char *argv[])
{
         return(0);
}

$ make x
cc     x.c   -o x
x.c:4:53: u-boot-1.1.4\include\configs\pxa255_idp.h: No such file or 
directory
make: *** [x] Error 1

Geek humor.  I gotta get a life! ;-)
gvb