* Updated Core TI-SDK setup and build instructions @ 2013-06-13 16:54 Denys Dmytriyenko 2013-06-13 18:36 ` Paul Kovitz 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2013-06-13 16:54 UTC (permalink / raw) To: meta-arago 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated Core TI-SDK setup and build instructions 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 0 siblings, 1 reply; 6+ messages in thread From: Paul Kovitz @ 2013-06-13 18:36 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org [-- Attachment #1: Type: text/plain, Size: 1238 bytes --] 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? Thanks. 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 > [-- Attachment #2: Type: text/html, Size: 1950 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated Core TI-SDK setup and build instructions 2013-06-13 18:36 ` Paul Kovitz @ 2013-06-13 19:06 ` Denys Dmytriyenko 2013-06-14 16:27 ` Paul Kovitz 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2013-06-13 19:06 UTC (permalink / raw) To: Paul Kovitz; +Cc: meta-arago@arago-project.org 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 > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated Core TI-SDK setup and build instructions 2013-06-13 19:06 ` Denys Dmytriyenko @ 2013-06-14 16:27 ` Paul Kovitz 2013-06-14 16:31 ` Denys Dmytriyenko 0 siblings, 1 reply; 6+ messages in thread From: Paul Kovitz @ 2013-06-14 16:27 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org [-- Attachment #1: Type: text/plain, Size: 1376 bytes --] I see the metadata file revisions are locked down. Still I have questions. I ran the oe-layertool-setup.sh script but still there are recipes, the ltp-ddt .bbappend files in sources/meta-arago/meta-arago-distro/recipes-devtools/ltp-ddt, that have SRCREV = "{AUTOREV}". I expected the automatically generated local.conf to contain something like SRCREV_pn-ltp-ddt = "70e324b8352e817485cc5e6865341c1a40118f78" (or some such SHA1) so I know I build the same ltp-ddt that was used to generate the SDK. Did I miss a step? Is there a configuration file somewhere else I did not find? To get the sources for the bitbake metadata, I ran git clone git://arago-project.org/git/projects/oe-layersetup.git amsdk cd amsdk /oe-layertool-setup.sh -f configs/amsdk/amsdk-05.07.00.00-config.txt Also, in meta-arago-extras/recipes-connectivity/wpa-supplicant/ wpa-supplicant_r5.00.18.bb, meta-arago-extras/recipes-connectivity/wpa-supplicant/ wpa-supplicant_r5.sp4.01.bb, meta-arago-extras/recipes-bsp/ti-compat-wireless/ ti-compat-wireless-wl12xx_r5.sp4.01.bb and meta-arago-extras/recipes-connectivity/hostap/hostap-daemon_r5.00.18.bbthere are SRCREV = "git tag" instead of a SHA1. This makes it harder to make a local source mirror. Would it be possible in the future releases to use the SHA1 and have a comment explaining the tag? Thanks for your help. [-- Attachment #2: Type: text/html, Size: 2389 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated Core TI-SDK setup and build instructions 2013-06-14 16:27 ` Paul Kovitz @ 2013-06-14 16:31 ` Denys Dmytriyenko 2013-06-14 16:39 ` Paul Kovitz 0 siblings, 1 reply; 6+ messages in thread From: Denys Dmytriyenko @ 2013-06-14 16:31 UTC (permalink / raw) To: Paul Kovitz; +Cc: meta-arago@arago-project.org On Fri, Jun 14, 2013 at 09:27:18AM -0700, Paul Kovitz wrote: > I see the metadata file revisions are locked down. Still I have questions. > > I ran the oe-layertool-setup.sh script but still there are recipes, the > ltp-ddt .bbappend files in > sources/meta-arago/meta-arago-distro/recipes-devtools/ltp-ddt, that have > SRCREV = "{AUTOREV}". > > I expected the automatically generated local.conf to contain something like > SRCREV_pn-ltp-ddt = "70e324b8352e817485cc5e6865341c1a40118f78" (or some > such SHA1) so I know I build the same ltp-ddt that was used to generate the > SDK. Yes, ltp-ddt is still AUTOREV-ed, unfortunately. But it is a test tool anyway and should not be part of the production system... We should probably look into pinning it as well for the releases - all other packages are pinned, as far as I know. > Did I miss a step? Is there a configuration file somewhere else I did not > find? To get the sources for the bitbake metadata, I ran > > git clone git://arago-project.org/git/projects/oe-layersetup.git amsdk > cd amsdk > /oe-layertool-setup.sh -f configs/amsdk/amsdk-05.07.00.00-config.txt > > Also, in meta-arago-extras/recipes-connectivity/wpa-supplicant/ > wpa-supplicant_r5.00.18.bb, > meta-arago-extras/recipes-connectivity/wpa-supplicant/ > wpa-supplicant_r5.sp4.01.bb, > meta-arago-extras/recipes-bsp/ti-compat-wireless/ > ti-compat-wireless-wl12xx_r5.sp4.01.bb and > meta-arago-extras/recipes-connectivity/hostap/hostap-daemon_r5.00.18.bbthere > are SRCREV = "git tag" instead of a SHA1. This makes it harder to > make a local source mirror. Would it be possible in the future releases to > use the SHA1 and have a comment explaining the tag? You mean this commit from last month? http://arago-project.org/git/?p=meta-arago.git;a=commitdiff;h=451145b70e1fd922d99ae98041d9801008b6d5bf -- Denys ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Updated Core TI-SDK setup and build instructions 2013-06-14 16:31 ` Denys Dmytriyenko @ 2013-06-14 16:39 ` Paul Kovitz 0 siblings, 0 replies; 6+ messages in thread From: Paul Kovitz @ 2013-06-14 16:39 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org [-- Attachment #1: Type: text/plain, Size: 171 bytes --] >You mean this commit from last month? > http://arago-project.org/git/?p=meta-arago.git;a=commitdiff;h=451145b70e1fd922d99ae98041d9801008b6d5bf Precisely! Thanks! [-- Attachment #2: Type: text/html, Size: 686 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-06-14 16:39 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2013-06-14 16:27 ` Paul Kovitz 2013-06-14 16:31 ` Denys Dmytriyenko 2013-06-14 16:39 ` Paul Kovitz
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.