From: Denys Dmytriyenko <denys@ti.com>
To: Paul Kovitz <paul.kovitz@welchallyn.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: Updated Core TI-SDK setup and build instructions
Date: Thu, 13 Jun 2013 15:06:47 -0400 [thread overview]
Message-ID: <20130613190647.GW3741@edge> (raw)
In-Reply-To: <CA+edY+RB9HN0JsPJecU1MNO1-5biRUNFqiEW82_q+ztJDtXe7A@mail.gmail.com>
On Thu, Jun 13, 2013 at 11:36:10AM -0700, Paul Kovitz wrote:
> Hi Denys.
>
> Overall, the wiki looks clear. I have some questions.
>
> The wiki does not address the SDK releases. I want to reproduce exactly
> amsdk-05.07.00.00. Do I use the arago 2011.09 toolchain or the linaro
> toolchain? Also, if I want to reproduce the amsdk-05.07.00.00 release when
> some recipes always get the latest from a git repo or a svn repo, is there
> a list of SRCREV overrides somewhere that I can put in my local.conf so I
> can be sure I build with the version that was tested and released rather
> than the latest version in the repo?
Paul,
Those are all good questions!
There are config files in oe-layersetup repository that correspond to specific
product releases (coresdk, amsdk and mcsdk). They usually point to the HEAD of
corresponding layers (same as arago-danny-config, for example) during
development phase, and locked down to specific tags or commit IDs once the
release is out. So, in order to reproduce amsdk-05.07.00.00, you'd need to use
a corresponding amsdk/amsdk-05.07.00.00-config file with oe-layertool-setup
script. That config file has all the layers locked down to specific tags and
commit IDs, so the setup doesn't change over time. It also uses amsdk-specific
integration copies of meta-ti and meta-arago repos for tagging purposes, or if
there were any last minute fixes/hacks that didn't go into official meta-ti
and meta-arago. amsdk-05.07.00.00 used the old Arago toolchain 2011.09, so if
you want to reproduce it exactly, you should use the same toolchain.
Please let me know if you have any additional questions. Thanks.
--
Denys
> On Thu, Jun 13, 2013 at 9:54 AM, Denys Dmytriyenko <denys@ti.com> wrote:
>
> > All,
> >
> > Here are the updated instructions on how to setup your build environment
> > for
> > the Yocto Project and OpenEmbedded in order to build our Core TI-SDK images
> > out of "meta-ti" TI BSP layer and "meta-arago" Arago Project distribution:
> >
> > http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment
> >
> > Please let me know of any comments, questions or feedback. Thanks.
> >
> > --
> > Denys
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> >
next prev parent reply other threads:[~2013-06-13 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 16:54 Updated Core TI-SDK setup and build instructions Denys Dmytriyenko
2013-06-13 18:36 ` Paul Kovitz
2013-06-13 19:06 ` Denys Dmytriyenko [this message]
2013-06-14 16:27 ` Paul Kovitz
2013-06-14 16:31 ` Denys Dmytriyenko
2013-06-14 16:39 ` Paul Kovitz
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=20130613190647.GW3741@edge \
--to=denys@ti.com \
--cc=meta-arago@arago-project.org \
--cc=paul.kovitz@welchallyn.com \
/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.