Re: Problem with image types

[Gary Thomas <gary@mlbassoc.com>]

On 2013-10-11 10:45, Eric Bénard wrote:
> Le Fri, 11 Oct 2013 10:18:38 -0600,
> Gary Thomas <gary@mlbassoc.com> a écrit :
>
>> On 2013-10-11 10:13, Eric Bénard wrote:
>>> Le Fri, 11 Oct 2013 09:37:48 -0600,
>>> Gary Thomas <gary@mlbassoc.com> a écrit :
>>>
>>>> On 2013-10-11 09:35, Eric Bénard wrote:
>>>>> Le Fri, 11 Oct 2013 08:52:30 -0600,
>>>>> Gary Thomas <gary@mlbassoc.com> a écrit :
>>>>>
>>>>>> On 2013-10-11 08:39, Chris Larson wrote:
>>>>>>>
>>>>>>> On Fri, Oct 11, 2013 at 7:38 AM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>>>>>>>
>>>>>>>        I'm using image_types_fsl from meta-fsl-arm and running into
>>>>>>>        some issues.  If I set
>>>>>>>           IMAGE_FSTYPES="tar.bz2 ext3 sdcard"
>>>>>>>           IMAGE_CLASSES="image_types_fsl"
>>>>>>>        I only end up with .ext3 and .sdcard images - no .tar.bz2.
>>>>>>>        If I use the default
>>>>>>>           IMAGE_CLASSES="image_types"
>>>>>>>        then I get .tar.bz2 but no .sdcard
>>>>>>>
>>>>>>>        How can I have them all at once?
>>>>>>>
>>>>>>>
>>>>>>> Note that IMAGE_CLASSES is plural, not singular :)
>>>>>>>
>>>>>>> IMAGE_CLASSES = "image_types image_types_fsl", presumably.
>>>>>>
>>>>>> When I tried that, I got the same results as just IMAGE_CLASSES="image_types"
>>>>>> Also, meta-fsl-arm/classes/image_types_fsl.bbclass inherits "image_types" so
>>>>>> I don't think it should be necessary to list them both.
>>>>>>
>>>>> don't you have a IMAGE_FSTYPES="ext3 sdcard" hardcoded somewhere in
>>>>> your machine file ?
>>>>
>>>> No, as seen above, IMAGE_FSTYPES="tar.bz2 ext3 sdcard"
>>>>
>>> bitbake yourimage -e may help to understand how IMAGE_FSTYPES is built.
>>
>> I had already done this - that's where the quoted values are from.  IMAGE_FSTYPES
>> definitely contains all three types, but only .ext3 and .sdcard are being
>> built if I use image_types_fsl.
>>
> strange I've launched a build for nitrogen6x to see if I reproduce the
> problem here.

I'm not sure what happened, but I just ran another build and now all is happy.
I must have made a typo or some such to cause my confusion.

Seems like it is working as expected - sorry for the noise.

> Usually I don't touch IMAGE_CLASSES but only IMAGE_FSTYPES
> (as IMAGE_CLASSES is set by IMAGE_CLASSES += "image_types_fsl"
> in ./conf/machine/include/fsl-default-settings.inc)


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