Re: [yocto] Does PACKAGECONFIG only apply to autotools recipes
On 21 March 2018 at 13:34, Alan Martinovic wrote: > Thanks. :) > I guess it's safe to say that it has a confined usage to recipes that > require > configuration before the compilation process. > > Like a source written in c using autotools as the build system for which > you > pass configure flags and would potentially need to pass library paths... > As opposed to a python recipe that doesn't need to be build. > Just to be that person who says "well, actually"... The piglit recipe uses PACKAGECONFIG and that is pure Python. You can still have a configure phase with Python code. Any recipe is welcome to use the PACKAGECONFIG variable, it just has to respect PACKAGECONFIG_CONFARGS which apart from a few recipes with entirely home-grown build systems is done in the classes. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Does PACKAGECONFIG only apply to autotools recipes
Thanks. :)
I guess it's safe to say that it has a confined usage to recipes that
require
configuration before the compilation process.
Like a source written in c using autotools as the build system for which
you
pass configure flags and would potentially need to pass library paths...
As opposed to a python recipe that doesn't need to be build.
On Thu, Mar 15, 2018 at 6:31 PM, Martin Jansa
wrote:
> It's applied in PACKAGECONFIG_CONFARGS variable and various bbclasses (and
> also various recipes) use this variable where needed, see git grep:
>
> meta/classes/base.bbclass:appendVar('PACKAGECONFIG_CONFARGS',
> extraconf)
>
> meta/classes/autotools.bbclass:EXTRA_OECONF_append = "
> ${PACKAGECONFIG_CONFARGS}"
> meta/classes/cmake.bbclass:EXTRA_OECMAKE_append = "
> ${PACKAGECONFIG_CONFARGS}"
> meta/classes/meson.bbclass:EXTRA_OEMESON += "${PACKAGECONFIG_CONFARGS}"
> meta/classes/waf.bbclass:EXTRA_OECONF_append = "
> ${PACKAGECONFIG_CONFARGS}"
>
> meta/recipes-graphics/glew/glew_2.1.0.bb:EXTRA_OEMAKE =
> "${PACKAGECONFIG_CONFARGS} \
>
> It used to be included in EXTRA_OECONF by default, before:
> http://git.openembedded.org/openembedded-core/commit/?id=
> c98fb5f5129e71829ffab4449b3d28082bc95ab4
>
> On Thu, Mar 15, 2018 at 6:22 PM, Alan Martinovic <
> alan.martino...@senic.com> wrote:
>
>> Hi,
>> is it true that that PACKAGECONFIG is only used
>> for recipes that inherit autoconf?
>>
>> Was trying to understand what they do in a recipe:
>> https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipe
>> s-connectivity/bluez5/bluez5.inc
>> and didn't really get what this was about until found
>> the autoconf reference mentioned in a book.
>>
>> So "features" as referenced in the mega manual:
>> https://www.yoctoproject.org/docs/2.4/mega-manual/mega-manua
>> l.html#var-PACKAGECONFIG
>> are the flags that will end up being passed to ./configure?
>>
>> However later in the recipe it's used to populate other variables
>>
>> NOINST_TOOLS = " \
>> ${@bb.utils.contains('PACKAGECONFIG', 'readline',
>> '${NOINST_TOOLS_READLINE}', '', d)} \
>> ${@bb.utils.contains('PACKAGECONFIG', 'testing',
>> '${NOINST_TOOLS_TESTING}', '', d)} \
>> ${@bb.utils.contains('PACKAGECONFIG', 'tools',
>> '${NOINST_TOOLS_BT}', '', d)} \
>> "
>>
>> Is the original assumption true (that it's an autoconf only thing)?
>> Is there a way to test that by grepping the code (didn't found
>> autoconf references when greping for PACKAGECONFIG in
>> bitbake -e bluez5)?
>>
>> Be Well :)
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Does PACKAGECONFIG only apply to autotools recipes
It's applied in PACKAGECONFIG_CONFARGS variable and various bbclasses (and
also various recipes) use this variable where needed, see git grep:
meta/classes/base.bbclass:appendVar('PACKAGECONFIG_CONFARGS',
extraconf)
meta/classes/autotools.bbclass:EXTRA_OECONF_append = "
${PACKAGECONFIG_CONFARGS}"
meta/classes/cmake.bbclass:EXTRA_OECMAKE_append = "
${PACKAGECONFIG_CONFARGS}"
meta/classes/meson.bbclass:EXTRA_OEMESON += "${PACKAGECONFIG_CONFARGS}"
meta/classes/waf.bbclass:EXTRA_OECONF_append = " ${PACKAGECONFIG_CONFARGS}"
meta/recipes-graphics/glew/glew_2.1.0.bb:EXTRA_OEMAKE =
"${PACKAGECONFIG_CONFARGS} \
It used to be included in EXTRA_OECONF by default, before:
http://git.openembedded.org/openembedded-core/commit/?id=c98fb5f5129e71829ffab4449b3d28082bc95ab4
On Thu, Mar 15, 2018 at 6:22 PM, Alan Martinovic
wrote:
> Hi,
> is it true that that PACKAGECONFIG is only used
> for recipes that inherit autoconf?
>
> Was trying to understand what they do in a recipe:
> https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/
> recipes-connectivity/bluez5/bluez5.inc
> and didn't really get what this was about until found
> the autoconf reference mentioned in a book.
>
> So "features" as referenced in the mega manual:
> https://www.yoctoproject.org/docs/2.4/mega-manual/mega-
> manual.html#var-PACKAGECONFIG
> are the flags that will end up being passed to ./configure?
>
> However later in the recipe it's used to populate other variables
>
> NOINST_TOOLS = " \
> ${@bb.utils.contains('PACKAGECONFIG', 'readline',
> '${NOINST_TOOLS_READLINE}', '', d)} \
> ${@bb.utils.contains('PACKAGECONFIG', 'testing',
> '${NOINST_TOOLS_TESTING}', '', d)} \
> ${@bb.utils.contains('PACKAGECONFIG', 'tools',
> '${NOINST_TOOLS_BT}', '', d)} \
> "
>
> Is the original assumption true (that it's an autoconf only thing)?
> Is there a way to test that by grepping the code (didn't found
> autoconf references when greping for PACKAGECONFIG in
> bitbake -e bluez5)?
>
> Be Well :)
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Does PACKAGECONFIG only apply to autotools recipes
Hi,
is it true that that PACKAGECONFIG is only used
for recipes that inherit autoconf?
Was trying to understand what they do in a recipe:
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/bluez5/bluez5.inc
and didn't really get what this was about until found
the autoconf reference mentioned in a book.
So "features" as referenced in the mega manual:
https://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#var-PACKAGECONFIG
are the flags that will end up being passed to ./configure?
However later in the recipe it's used to populate other variables
NOINST_TOOLS = " \
${@bb.utils.contains('PACKAGECONFIG', 'readline',
'${NOINST_TOOLS_READLINE}', '', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'testing',
'${NOINST_TOOLS_TESTING}', '', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'tools',
'${NOINST_TOOLS_BT}', '', d)} \
"
Is the original assumption true (that it's an autoconf only thing)?
Is there a way to test that by grepping the code (didn't found
autoconf references when greping for PACKAGECONFIG in
bitbake -e bluez5)?
Be Well :)
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
