A question about overrides

A question about overrides

[Gary Thomas]

I have my own distribution layer, built on the poky distribution.
In other words, my layer defines a few basic setups, then inherits
poky to do the rest.

For the most part, I've been successful with this.  The problem at
hand is that for my distribution, I need to support a couple of
different architectures and at the moment, one of them needs to
stay in the stone age tools-wise.  In my distro.conf, I have
lines like these to select those tools for just that architecture:
   GCCVERSION_armv7a ?= "4.3.3"
This works for everything (I've tried), except this:
   POKYLIBC_armv7a ?= "glibc"

* Is there some magic I'm missing with regard to the 'POKYLIBC' symbol?
* Perhaps there's some other way?

For now, I'm overriding this in local.conf, but that requires
hand tuning that I'd like to avoid.

Thanks for any pointers

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: A question about overrides

[Richard Purdie]

On Fri, 2010-11-05 at 05:48 -0600, Gary Thomas wrote:
> I have my own distribution layer, built on the poky distribution.
> In other words, my layer defines a few basic setups, then inherits
> poky to do the rest.
> 
> For the most part, I've been successful with this.  The problem at
> hand is that for my distribution, I need to support a couple of
> different architectures and at the moment, one of them needs to
> stay in the stone age tools-wise.  In my distro.conf, I have
> lines like these to select those tools for just that architecture:
>    GCCVERSION_armv7a ?= "4.3.3"
> This works for everything (I've tried), except this:
>    POKYLIBC_armv7a ?= "glibc"
> 
> * Is there some magic I'm missing with regard to the 'POKYLIBC' symbol?
> * Perhaps there's some other way?
> 
> For now, I'm overriding this in local.conf, but that requires
> hand tuning that I'd like to avoid.

Can you be more specific about what your distro.conf file says? I'm
guessing you're requiring poky.conf in there? Are you setting the value
after the require and does it work if you do it beforehand?

I ask as that variable is used in a require in poky.conf, effectively
causing an immediate expansion of the variable so it needs to be set
before poky.conf, not afterwards.

Cheers,

Richard

Re: A question about overrides

[Gary Thomas]

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

On 11/10/2010 06:42 AM, Richard Purdie wrote:
> On Fri, 2010-11-05 at 05:48 -0600, Gary Thomas wrote:
>> I have my own distribution layer, built on the poky distribution.
>> In other words, my layer defines a few basic setups, then inherits
>> poky to do the rest.
>>
>> For the most part, I've been successful with this.  The problem at
>> hand is that for my distribution, I need to support a couple of
>> different architectures and at the moment, one of them needs to
>> stay in the stone age tools-wise.  In my distro.conf, I have
>> lines like these to select those tools for just that architecture:
>>     GCCVERSION_armv7a ?= "4.3.3"
>> This works for everything (I've tried), except this:
>>     POKYLIBC_armv7a ?= "glibc"
>>
>> * Is there some magic I'm missing with regard to the 'POKYLIBC' symbol?
>> * Perhaps there's some other way?
>>
>> For now, I'm overriding this in local.conf, but that requires
>> hand tuning that I'd like to avoid.
>
> Can you be more specific about what your distro.conf file says? I'm
> guessing you're requiring poky.conf in there? Are you setting the value
> after the require and does it work if you do it beforehand?
>
> I ask as that variable is used in a require in poky.conf, effectively
> causing an immediate expansion of the variable so it needs to be set
> before poky.conf, not afterwards.

Yes, I do have a require poky.conf and I'm setting these variables
before that statement.

I've attached the files I use (slightly sanitized).  Note that the only
way I could work this out was to define POKYLIBC in local.conf

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: mydistro.conf --]
[-- Type: text/plain, Size: 460 bytes --]

# My localized, layered distribution

require conf/distro/include/mydistro-fixed-revisions.inc
require conf/distro/poky.conf

DISTRO = "mydistro"
DISTRO_NAME = "My Local Embedded (Poky Powered)"
DISTRO_VERSION = "0.99+snapshot-${DATE}"

# Allow hardware overrides, e.g. armv7a
OVERRIDES .= ":${FEED_ARCH}:${SOC_FAMILY}"

# Use A&M kernels
PREFERRED_PROVIDER_virtual/kernel = "linux-mydistro"

# Use A&M opkg setup
EXTRAOPKGCONFIG = "mydistro-feed-config-opkg"

[-- Attachment #3: mydistro-fixed-revisions.inc --]
[-- Type: text/plain, Size: 412 bytes --]

#
# Override pinned versions (these variables are used by Poky)
#

#
# Note: only ARM uses old, fixed tools (because of TI packages)
#
GCCVERSION_armv7a ?= "4.3.3"
SDKGCCVERSION_armv7a ?= "4.3.3"
#BINUVERSION ?= "2.20.1"
BINUVERSION_armv7a = "2.18.50.0.7"
GLIBCVERSION_armv7a ?= "2.10.1"
LINUXLIBCVERSION_armv7a ?= "2.6.34"

# FIXME? Override this in local.conf
POKYLIBC ?= "eglibc"

SRCREV_pn-ffmpeg = "24596"