Re: [Angstrom-devel] [next][PATCH] setup-scripts: Add meta-linaro to EXTRALAYERS

[Denys Dmytriyenko]

On Tue, May 15, 2012 at 03:10:11PM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj 

Acked-by: Denys Dmytriyenko 


> ---
>  conf/bblayers.conf |4 +++-
>  sources/layers.txt |1 +
>  2 files changed, 4 insertions(+), 1 deletions(-)
> 
> diff --git a/conf/bblayers.conf b/conf/bblayers.conf
> index 3fdcf03..6d64dd5 100644
> --- a/conf/bblayers.conf
> +++ b/conf/bblayers.conf
> @@ -45,7 +45,9 @@ BSPLAYERS ?= " \
>  
>  # Add your overlay location to EXTRALAYERS
>  # Make sure to have a conf/layers.conf in there
> -EXTRALAYERS ?= ""
> +EXTRALAYERS ?= " \
> +  ${TOPDIR}/sources/meta-linaro \
> +"
>  
>  BBLAYERS = " \
>${TOPDIR}/sources/meta-angstrom \
> diff --git a/sources/layers.txt b/sources/layers.txt
> index a7414fe..1d2d696 100644
> --- a/sources/layers.txt
> +++ b/sources/layers.txt
> @@ -17,4 +17,5 @@ 
> meta-mozilla,git://github.com/OSSystems/meta-mozilla.git,master,HEAD
>  meta-chromium,git://github.com/eukrea/meta-chromium.git,master,HEAD
>  meta-mono,git://github.com/KokoFitClub/meta-mono.git,master,HEAD
>  
> meta-kde,git://gitorious.org/openembedded-core-layers/meta-kde.git,master,HEAD
> +meta-linaro,git://git.linaro.org/people/kwerner/meta-linaro.git,master,HEAD
>  openembedded-core,git://github.com/openembedded/oe-core.git,master,HEAD
> -- 
> 1.7.5.4
> 
> 
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] [next][PATCH] setup-scripts: Add meta-linaro to EXTRALAYERS

[Khem Raj]

Signed-off-by: Khem Raj 
---
 conf/bblayers.conf |4 +++-
 sources/layers.txt |1 +
 2 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/conf/bblayers.conf b/conf/bblayers.conf
index 3fdcf03..6d64dd5 100644
--- a/conf/bblayers.conf
+++ b/conf/bblayers.conf
@@ -45,7 +45,9 @@ BSPLAYERS ?= " \
 
 # Add your overlay location to EXTRALAYERS
 # Make sure to have a conf/layers.conf in there
-EXTRALAYERS ?= ""
+EXTRALAYERS ?= " \
+  ${TOPDIR}/sources/meta-linaro \
+"
 
 BBLAYERS = " \
   ${TOPDIR}/sources/meta-angstrom \
diff --git a/sources/layers.txt b/sources/layers.txt
index a7414fe..1d2d696 100644
--- a/sources/layers.txt
+++ b/sources/layers.txt
@@ -17,4 +17,5 @@ 
meta-mozilla,git://github.com/OSSystems/meta-mozilla.git,master,HEAD
 meta-chromium,git://github.com/eukrea/meta-chromium.git,master,HEAD
 meta-mono,git://github.com/KokoFitClub/meta-mono.git,master,HEAD
 meta-kde,git://gitorious.org/openembedded-core-layers/meta-kde.git,master,HEAD
+meta-linaro,git://git.linaro.org/people/kwerner/meta-linaro.git,master,HEAD
 openembedded-core,git://github.com/openembedded/oe-core.git,master,HEAD
-- 
1.7.5.4


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [yocto] Fwd: Narcissus update <- IMPORTANT

[Denys Dmytriyenko]

On Tue, May 15, 2012 at 01:15:05PM +0200, Koen Kooi wrote:
> 
> Op 15 mei 2012, om 12:24 heeft Koen Kooi het volgende geschreven:
> 
> > Apologies for the massive cross-post, but most users don't read the 
> > development lists :) To avoid 'reply all' mistakes the addressed lists are 
> > in BCC. In case you are wondering which lists: the beagleboard list, the 
> > meta-ti list and the yocto project list.
> 
> And I win the idiot of the week award for posting from an address that is 
> subscribed to none of those lists. *sigh*

Congratulations! :)

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] do you support Beagleboard-xM

[Kevin]

Hi, Gary:

We actually have built a GIT server internally, and my Ubuntu 10.04LTS is
able to get what I need from that internal machine.

However, when trying to get external source, git somehow doesn't work. It
even fails when trying to get your setup-scripts:

$ git clone git://github.com/Angstrom-distribution/setup-scripts.git
Initialized empty Git repository in
/home/dongk/Downloads/OE/Angstrom-distribution-setup-scripts-9d8c395/setup-scripts/.git/
github.com[0: 207.97.227.239]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)

I can download that scripts from your http link, unzip it to
"Angstrom-distribution-setup-scripts-9d8c395" folder and run from there.
However, so far I run into lots of errors.

My question is: with such situation, is it still possible to modify the
included oebb.sh with free http proxy and then rebuild Angstrom for BBxM on
my local Ubuntu10.04LTS machine?

Thanks!

Kevin




> Just because your IT team doesn't support GIT, why not just build or
> install it yourself?  What's your build host?
>
>
> --
> --**--
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> --**--
>
> __**_
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@**linuxtogo.org
> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**
> angstrom-distro-devel
>
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Time based version numbering of packages?

[Hauser, Wolfgang (external)]

Hi Bryan,

id did this in following way:

in recipe (or an amend.inc / .bbappend)

#to set it by default
XYZ_DATE ?= "${DATETIME}"

#set Package version
PV = "${XYZ_DATE}" 

#or add to existing
PV_append = "-${XYZ_DATE}" 

This needs following setting in environment to be able to set the date
from shell:

#Use following variables from environment in BitBake
export BB_ENV_EXTRAWHITE="MACHINE DISTRO OETREE OEBASE ANGSTROM_MODE
ANGSTROMLIBC LIBC XYZ_DATE"

then it is possible to build per day for example. 
export XYZ_DATE="$(date +"%Y%m%d")"

the version has the following style then: "-20120515-r4" or
"-1.2.3-20120515-r4"


Regards,

Wolfgang

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Time based version numbering of packages?

[Koen Kooi]

Op 15 mei 2012, om 16:33 heeft Bryan Evenson het volgende geschreven:

> Does anyone out there have a setup that creates a unique build number and 
> works with bitbake?  I'm not married to the idea of using the date; I just 
> want to ensure that if I see two boards that have the same version number, 
> that they are really running the same binary. 

If you use OE, that's what PV and PR are for. If PV and PR match, but the 
binaries are different your build process is broken, adding a timestamp in 
PV/PR isn't going to help with that.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

[Angstrom-devel] Time based version numbering of packages?

[Bryan Evenson]

All,

Before starting with the Angstrom toolchain, we had a general version numbering 
scheme setup with the intent of ensuring that if the version number of our 
application on two machines were the same, you truly were running the same 
build.  We're having issues figuring out to modify our development processes to 
fit in with the Angstrom development workflow.  I'm looking for suggestion on 
how other groups tackle this issue.  Every place I've looked through 
theOpenEmbedded/Bitbake/Angstrom manuals have a big "TODO" in any section 
related to this topic.  

What I would like to do is have a suffix on the version number that relates to 
the build time.  So when you do 'opkg info foo' on the development system, 
instead of reporting a version number of "1.0.3-r0.9" it would look something 
like "1.0.3+20120515080010-r0.9" to indicate that it was built on May 15, 2012 
at 8:00:10 AM.  The problem is that I can't figure out where to have bitbake 
insert the build time and then properly create the package.  I believe I'd need 
to have the version number ${PV} modified with a do_compile_prepend() action in 
my bitbake recipe.  However, I haven't found a good way to do this without 
breaking the packaging process.

Does anyone out there have a setup that creates a unique build number and works 
with bitbake?  I'm not married to the idea of using the date; I just want to 
ensure that if I see two boards that have the same version number, that they 
are really running the same binary.  Any suggestions are welcome.

Thanks,
Bryan

___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] [yocto] Fwd: Narcissus update <- IMPORTANT

[Koen Kooi]

Op 15 mei 2012, om 12:24 heeft Koen Kooi het volgende geschreven:

> Apologies for the massive cross-post, but most users don't read the 
> development lists :) To avoid 'reply all' mistakes the addressed lists are in 
> BCC. In case you are wondering which lists: the beagleboard list, the meta-ti 
> list and the yocto project list.

And I win the idiot of the week award for posting from an address that is 
subscribed to none of those lists. *sigh*
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Re: [Angstrom-devel] Narcissus update <- IMPORTANT

[Koen Kooi]

Op 3 mei 2012, om 13:04 heeft Philip Balister het volgende geschreven:

> On 05/03/2012 05:49 AM, Koen Kooi wrote:
>> The process to add machines is fairly simple:
>> 
>> 1) Find the layer for the machine in 
>> http://www.openembedded.org/wiki/LayerIndex
>> 2) Check the setup scripts to see if it's already configured
>> 3) Send patch for setupscripts
>> 4) Send patch for narcissus
> 
> Does anyone know a good way to collect votes from users interested in
> machines, but unable to commit to supporting them? This would be useful
> feedback for people interested in adding machines back.
> 
> As we add machines back, I'd like to see two things:
> 
> 1) No machine added unless someone is willing to handle questions on the
> lists.

Agreed

> 2) No machines added unless we know people want to use it.

Agreed

> I'd like to see more focus on getting Angstrom working well for a
> "reasonable" set of machines, and less focus on supporting every
> available combination of inits/libcs/machines.

So far the complainers about certain init systems fall in the 
complainers-not-doers category, so the v2012.05 release will only support 1 
init system and 1 libc, but multiple machines. The next release will likely add 
1.5 libcs: uclibc and klibc since we have people actively maintaining that in 
oe-core and meta-oe. Any extra features are up to the people willing to do the 
work.

FWIW I've moved from a silicon vendor to a hardware company, so I'm less 
focussed on bleeding edge silicon support and more on making long term 
maintenance easier. Now that we actually have a release branch as well as 
release branches for various layers we use the load is spread between a lot 
more people than it was in the past. This means there now is not only 
motivation but actually time to solicit feedback on the releases and how people 
use them. So:

Please share your feedback and things you want to see changed.

regards,

Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel