[Haiku-commits] r31317 - in buildtools/branches/32bit-wchar_t: gcc/gcc/config gcc/gcc/config/arm gcc/gcc/config/i386 gcc/gcc/config/m68k gcc/gcc/config/mips gcc/gcc/config/rs6000 legacy/binutils/bfd legacy/gcc/gcc legacy/gcc/gcc/config/i386

Ingo Weinhold ingo_weinhold at gmx.de
Mon Jun 29 23:10:19 CEST 2009


-------- Original-Nachricht --------
> Datum: Mon, 29 Jun 2009 23:01:16 +0200
> Von: Oliver Tappe <zooey at hirschkaefer.de>
> 
> On 2009-06-29 at 22:30:12 [+0200], Axel Dörfler <axeld at pinc-software.de> 
> wrote:
> > zooey at BerliOS <zooey at mail.berlios.de> wrote:
> > > * gcc4: removed /boot/home/config/include from gcc's default include
> > > paths,
> > >   as I find it rather awkward to have a user specific folder in that
> > > list
> > 
> > While /boot/home/... is indeed not a good choice, what about ~/...
> > then? 
> 
> Will that even work at all (i.e. isn't the tilde expanded by the shell
> only)?

I doubt it. Maybe the compiler expands environmental variables, so perhaps ${HOME} has a better chance.

> > I think it's at least convenient to have it in the default
> > directories.
> 
> Well, it was only included in gcc4, but never for any gcc2 versions I know
> of. Most applications add that folder in their buildsystem (switching to 
> /boot/common for haiku, though).
> 
> That being said, I'm not strictly against including 
> /boot/home/config/include. 

I don't think there's much point adding it. With the install prefix changed to /boot/common the /boot/home/config/include directory will be unused unless one tinkers with it oneself.

CU, Ingo



More information about the Haiku-commits mailing list