All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Stiffler <j-stiffler@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH 2/2] ti-xdais: Add version 7.24.00.04
Date: Thu, 28 May 2015 12:27:54 -0400	[thread overview]
Message-ID: <5567420A.7060308@ti.com> (raw)
In-Reply-To: <55674045.9080509@ti.com>



On 5/28/2015 12:20 PM, 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"?
>

Just looked more into this... It got pulled in because I was including a 
dev package in the filesystem.

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



  reply	other threads:[~2015-05-28 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 14:09 [PATCH 1/2] ti-xdais: Move LIC_FILES_CHKSUM into recipe Jacob Stiffler
2015-05-08 14:09 ` [PATCH 2/2] ti-xdais: Add version 7.24.00.04 Jacob Stiffler
2015-05-08 16:23   ` Khem Raj
2015-05-08 17:17     ` Jacob Stiffler
2015-05-19 20:11       ` Denys Dmytriyenko
2015-05-20 10:29         ` Jacob Stiffler
2015-05-22 18:12           ` Denys Dmytriyenko
2015-05-28 16:20             ` Jacob Stiffler
2015-05-28 16:27               ` Jacob Stiffler [this message]
2015-05-29 19:37               ` Denys Dmytriyenko
2015-06-01 12:52                 ` Jacob Stiffler
2015-06-01 13:33                   ` Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5567420A.7060308@ti.com \
    --to=j-stiffler@ti.com \
    --cc=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.