On Mon, Aug 19, 2013 at 11:40 PM, Paul D. DeRocco <pdero...@ix.netcom.com>wrote:
> I suspect what happened is that support for the "subdir=" option on local > files was added in 2009, then someone thought, why have this obscure > syntax? Simpler to impose the directory structure on the local files in > the metadata, allow file:// to refer to any pathname, not just a filename, > and have the file copy routine create any necessary subdirectories in the > build tree. So they took that option out. Just a guess. > We've always supported directories in file:// uris. The unpacking process was moved from base.bbclass into the bitbake fetchers. See https://github.com/openembedded/bitbake/blob/master/lib/bb/fetch2/__init__.py#L1234-L1240. Not sure why it didn't work for you, though. I'm guessing it has to do with the way it changes the current working directory before running the command, rather than directly altering the destination directory — if the command being run uses an absolute path, the current working directory wouldn't affect anything. *shrug* -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
