[oe] COMPATIBLE_MACHINE
I'm writing a .bbappend for a recipe which contains a COMPATIBLE_MACHINE pattern like this: COMPATIBLE_MACHINE = (machine1|machine2|machine3) Is there a way my .bbappend file can add to this pattern? I don't want to disturb what's there, just add my machine as well. Thanks -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE
On Fri, 2012-04-20 at 07:20 -0600, Gary Thomas wrote: I'm writing a .bbappend for a recipe which contains a COMPATIBLE_MACHINE pattern like this: COMPATIBLE_MACHINE = (machine1|machine2|machine3) Is there a way my .bbappend file can add to this pattern? I don't want to disturb what's there, just add my machine as well. COMPATIBLE_MACHINE .= |machine4 p. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE
On Fri, Apr 20, 2012 at 6:20 AM, Gary Thomas g...@mlbassoc.com wrote: I'm writing a .bbappend for a recipe which contains a COMPATIBLE_MACHINE pattern like this: COMPATIBLE_MACHINE = (machine1|machine2|machine3) Is there a way my .bbappend file can add to this pattern? I don't want to disturb what's there, just add my machine as well. It's just a standard regular expression. COMPATIBLE_MACHINE = (machine1|machine2|machine3) COMPATIBLE_MACHINE .= |machine4 Will result in a value of (machine1|machine2|machine3)|machine4, which is still a perfectly valid pattern, as far as I can tell. -- Christopher Larson ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE
On 2012-04-20 08:04, Chris Larson wrote: On Fri, Apr 20, 2012 at 6:20 AM, Gary Thomasg...@mlbassoc.com wrote: I'm writing a .bbappend for a recipe which contains a COMPATIBLE_MACHINE pattern like this: COMPATIBLE_MACHINE = (machine1|machine2|machine3) Is there a way my .bbappend file can add to this pattern? I don't want to disturb what's there, just add my machine as well. It's just a standard regular expression. COMPATIBLE_MACHINE = (machine1|machine2|machine3) COMPATIBLE_MACHINE .= |machine4 Will result in a value of (machine1|machine2|machine3)|machine4, which is still a perfectly valid pattern, as far as I can tell. Yes, this does seem to work. Any clues why most uses of COMPATIBLE_MACHINE use the regex (x|y|z) instead of just x|y|z? Aren't they the same? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE
On Fri, Apr 20, 2012 at 7:15 AM, Gary Thomas g...@mlbassoc.com wrote: On 2012-04-20 08:04, Chris Larson wrote: On Fri, Apr 20, 2012 at 6:20 AM, Gary Thomasg...@mlbassoc.com wrote: I'm writing a .bbappend for a recipe which contains a COMPATIBLE_MACHINE pattern like this: COMPATIBLE_MACHINE = (machine1|machine2|machine3) Is there a way my .bbappend file can add to this pattern? I don't want to disturb what's there, just add my machine as well. It's just a standard regular expression. COMPATIBLE_MACHINE = (machine1|machine2|machine3) COMPATIBLE_MACHINE .= |machine4 Will result in a value of (machine1|machine2|machine3)|machine4, which is still a perfectly valid pattern, as far as I can tell. Yes, this does seem to work. Any clues why most uses of COMPATIBLE_MACHINE use the regex (x|y|z) instead of just x|y|z? Aren't they the same? They are. No idea why people use the grouping. -- Christopher Larson ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE and no buildable providers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18-09-10 13:53, Frans Meulenbroeks wrote: Or should COMPATIBLE_MACHINE be allowed to trickle up so when building a recipe that depends on another recipe that is not for that MACHINE one only gets a warning. It should. COMPATIBLE_MACHINE should only be added to recipes that are built for a certain arch/machine, not to the dependants. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMlhZBMkyGM64RGpERAsA+AJ4w0yjcOtk4JH4uOndXgAeLfZjo4QCgtNI/ C5epydrnht1zRlcSg0/21nI= =e5ms -END PGP SIGNATURE- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE and no buildable providers
2010/9/19 Koen Kooi k.k...@student.utwente.nl: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18-09-10 13:53, Frans Meulenbroeks wrote: Or should COMPATIBLE_MACHINE be allowed to trickle up so when building a recipe that depends on another recipe that is not for that MACHINE one only gets a warning. It should. COMPATIBLE_MACHINE should only be added to recipes that are built for a certain arch/machine, not to the dependants. How can we arrange this? It is way out of my league to implement this. Any takers? Frans ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] COMPATIBLE_MACHINE and no buildable providers
Bumped upon the folliwing issue. If a recipe depends on another recipe but that one does have a COMPATIBLE_MACHINE and you are not in the list, you get an error like: ERROR: Required build target xyz' has no buildable providers. Is this desired? Or in other words: should this be fixed by adding the COMPATIBLE_MACHINE clause to the recipe that has the depends? Or should COMPATIBLE_MACHINE be allowed to trickle up so when building a recipe that depends on another recipe that is not for that MACHINE one only gets a warning. This is for instance an issue when doing bitbake world. Frans ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] COMPATIBLE_MACHINE - how can use?
COMPATIBLE_MACHINE uses Python's re.match(), so COMPATIBLE_MACHINE is a regular expression that must match the start of the MACHINE variable. For instance, from recipes/linux/linux-davinci_2.6.30.bb: COMPATIBLE_MACHINE = (dm6446-evm|dm6467-evm|dm355-evm|davinci-sffsdr|dm355-leopard) The following line would have much the same effect: COMPATIBLE_MACHINE = (dm6446|dm6467|dm355|davinci) If you try to build this recipe for any non-matching MACHINE, it will refuse. Additionally, if MACHINE=dm6446-evm and you ask for a build of the kernel, only three recipes are compatible: * linux-davinci_2.6.28.bb * linux-davinci_2.6.30.bb * linux-davinci_git.bb The one that actually gets built will be chosen either alphanumerically, or by respecting the DEFAULT_PREFERENCE or PREFERRED_VERSION variables. Hope this helps, Douglas. Leo wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi at all, It's not long ago that I use OE and some things do not know very well.. :D For example, can someone explain me how (and where) can use COMPATIBLE_MACHINE? thanks a lot for all response! :D hachreak ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
