[meta-ti] [PATCH 2/2] ti-xdais: Add version 7.24.00.04

[Jacob Stiffler]

On 5/29/2015 3:37 PM, Denys Dmytriyenko wrote:
> On Thu, May 28, 2015 at 12:20:21PM -0400, Jacob Stiffler wrote:
>>
>> On 5/22/2015 2:12 PM, Denys Dmytriyenko wrote:
>>> On Wed, May 20, 2015 at 06:29:46AM -0400, Jacob Stiffler wrote:
>>>> On 5/19/2015 4:11 PM, Denys Dmytriyenko wrote:
>>>>> On Fri, May 08, 2015 at 01:17:42PM -0400, Jacob Stiffler wrote:
>>>>>> I was following the precedent set by existing RTOS packages (See
>>>>>> recipes-ti/xdais/ti-xdais_6.26.01.03.bb).
>>>>>>
>>>>>> These RTOS packages are build only dependencies, and they do not get
>>>>>> installed into the target filesystem. They are primarily used for
>>>>>> building firmware.
>>>>> Should they be "-native" then?
>>>>>
>>>> I suppose they should be, but this is how is was done before.
>>>>
>>>> If you look at recipes-ti/includes/ti-paths.inc, you'll see that all
>>>> paths point into STAGING_DIR_TARGET
>>> Ok, we may end up doing this on the target at some point.
>>> Can we simply FILES_${PN} += "*" to pick up everything installed and shove it
>>> into the package? That way we won't need INSANE_SKIP and the build deps can be
>>> used on the target in the future...
>>>
>> Adding all of these files to the ${PN} package causes them to be
>> pulled into the filesystem. Should these instead go into the
>> ${PN}-dev package (they are purely development files), and then
>> ALLOW_EMPTY_${PN} = "1"?
> Actually, that's a good idea. Should we modify other recipes similarly, when
> they only provide build dependencies for DSP?
>

It seems this would make the most sense.

Should I submit patches for the recently updated packages which would be 
effected? They are the following:
* ti-sysbios
* ti-xdais

I'm not sure about ti-xdctools since this includes xdc and other utilities.

>>>>>> On 5/8/2015 12:23 PM, Khem Raj wrote:
>>>>>>>> On May 8, 2015, at 7:09 AM, Jacob Stiffler <j-stiffler at ti.com> wrote:
>>>>>>>>
>>>>>>>> +INSANE_SKIP_${PN} = "installed-vs-shipped"
>>>>>>> can this be fixed instead ?
>>>>>> -- 
>>>>>> _______________________________________________
>>>>>> meta-ti mailing list
>>>>>> meta-ti at yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/meta-ti