On 05/25/2011 02:31 PM, Richard Purdie wrote: > On Wed, 2011-05-25 at 13:04 -0700, Darren Hart wrote: >> >> On 05/25/2011 12:11 PM, Phil Blundell wrote: >>> On Wed, 2011-05-25 at 11:56 -0700, Darren Hart wrote: >>>> If it is indeed space separated then I should be able to remedy both >>>> issues by simply using the append operator and not self-referencing. >>>> Correct? >>> >>> I think that's true, yes. But, space separation is fairly undesirable >>> for anything involving paths (particularly absolute ones) and it is >>> tempting to say that we should change that variable to have a different >>> separator. >>> >> >> The only example I see of concatenating this variable is a prepend which >> uses colons. RP also mentioned he was pretty sure it should be colons. >> I'll figure it out for certain and fix the path assignments in meta-intel. > > I checked the code and it is currently setup to use spaces but all the > users I've seen use colons. > > There is significant precedent for *PATH* variables (FILESPATH, BBPATH, > PATH) being colon delimited so I'm tempted to say the utils.bbclass code > handling this should be fixed for EXTRAFILESPATH. > > Also, the self referencing of that variable is correct. What is missing > is a default value for it, again that needs fixing in the core...
I've sent a patch that I believe works. http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003145.html -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
