2010/9/15 Philip Balister <[email protected]>: > On 09/15/2010 02:32 AM, Frans Meulenbroeks wrote: >> >> 2010/9/15 Graham Gower<[email protected]>: >>> >>> Recipes are broken for all architectures except one (probably arm) >>> because the files in the SRC_URI depend on TARGET_ARCH and the md5/sha256 >>> are presumably valid only for one of these. >>> >>> Anyone wanting perforce should submit new recipes for new perforce >>> versions. >>> >>> Signed-off-by: Graham Gower<[email protected]> >> >> Agree with the reasoning of Graham, so: >> >> Acked-by: Frans Meulenbroeks<[email protected]> >> >> Actually I am not too keen on having recipes that just "install" an >> externally downloaded binary blob >> (and functionally speaking this does not seem to be something for an >> embedded system either) > > I will have a need for a recipe to install binary blobs (fpga bin files) > into a file system at some point. So this class recipes are needed. > > Philip
I'm not saying it should be made technically impossible or so. Actually I do have recipes that install fpga images too, but these live in an overlay. As I do actual product development with oe I am just not too keen on pulling binary stuff from elsewhere. And rereading my message I can imagine some misunderstanding. I wrote >> (and functionally speaking this does not seem to be something for an >> embedded system either) and with this, I wanted to refer to the functionality provided by P4 (a high end SCM if I grasp it right), not to binary recipes in general. Apologies for the confusion. Frans _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
