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

2015-06-01 Thread Denys Dmytriyenko
On Mon, Jun 01, 2015 at 08:52:45AM -0400, Jacob Stiffler wrote:
 
 
 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

Let me push what I already have to not delay it any longer. Please send a 
followup patch to update FILES_${PN}-dev - could be a single patch across 
recipes. Thanks.


 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-stiff...@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
 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


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

2015-05-29 Thread Denys Dmytriyenko
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?


 On 5/8/2015 12:23 PM, Khem Raj wrote:
 On May 8, 2015, at 7:09 AM, Jacob Stiffler j-stiff...@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
 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


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

2015-05-28 Thread Jacob Stiffler



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?



On 5/8/2015 12:23 PM, Khem Raj wrote:

On May 8, 2015, at 7:09 AM, Jacob Stiffler j-stiff...@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


--
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


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

2015-05-22 Thread Denys Dmytriyenko
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...


 On 5/8/2015 12:23 PM, Khem Raj wrote:
 On May 8, 2015, at 7:09 AM, Jacob Stiffler j-stiff...@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
 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


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

2015-05-08 Thread Jacob Stiffler
Signed-off-by: Jacob Stiffler j-stiff...@ti.com
---
 recipes-ti/xdais/ti-xdais_7.24.00.04.bb |   10 ++
 1 file changed, 10 insertions(+)
 create mode 100644 recipes-ti/xdais/ti-xdais_7.24.00.04.bb

diff --git a/recipes-ti/xdais/ti-xdais_7.24.00.04.bb 
b/recipes-ti/xdais/ti-xdais_7.24.00.04.bb
new file mode 100644
index 000..0f27514
--- /dev/null
+++ b/recipes-ti/xdais/ti-xdais_7.24.00.04.bb
@@ -0,0 +1,10 @@
+require ti-xdais.inc
+
+PV = 7_24_00_04
+
+LIC_FILES_CHKSUM = 
file://xdais_7_24_00_04_Manifest.html;md5=fd16442230745f0877cfe1c622669fd6
+
+SRC_URI[xdaistarball.md5sum] = f7514085b531f2ae49b37b30194e4989
+SRC_URI[xdaistarball.sha256sum] = 
79fd30377ab4c497292aeefb0565f81703d9020d1242b02ca9968c561e0de9a1
+
+INSANE_SKIP_${PN} = installed-vs-shipped
-- 
1.7.9.5

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


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

2015-05-08 Thread Jacob Stiffler
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.


On 5/8/2015 12:23 PM, Khem Raj wrote:

On May 8, 2015, at 7:09 AM, Jacob Stiffler j-stiff...@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


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

2015-05-08 Thread Khem Raj

 On May 8, 2015, at 7:09 AM, Jacob Stiffler j-stiff...@ti.com wrote:
 
 +INSANE_SKIP_${PN} = installed-vs-shipped

can this be fixed instead ?


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti