From: Denys Dmytriyenko <denys@ti.com>
To: Ash Charles <ashcharles@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 2/6] Set ${TOOLCHAIN_PATH} used by some recipes
Date: Mon, 23 Jun 2014 18:33:33 -0400 [thread overview]
Message-ID: <20140623223333.GL6700@edge> (raw)
In-Reply-To: <CAK8F28mucmU73EWJOWtBpCd60kBhGv97q-Vn0oGNT5U0hsUfxw@mail.gmail.com>
Well, I set it in our Arago distro based on the toolchain used, but since
meta-ti is not a distro, I was thinking it should provide a safe default, but
conditional. In other words, changing your patch to conditional assignment ?=
should be good enough...
--
Denys
On Mon, Jun 23, 2014 at 03:30:10PM -0700, Ash Charles wrote:
> Good point. Where is the right place to set the toolchain path? Or
> perhaps the recipes shouldn't use it at all?
>
> --Ash
>
> On Mon, Jun 23, 2014 at 3:05 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> > This one is not correct and will break with an external toolchain...
> >
> > On Fri, Jun 13, 2014 at 03:34:04PM -0700, Ash Charles wrote:
> >> Signed-off-by: Ash Charles <ashcharles@gmail.com>
> >> ---
> >> recipes-ti/includes/ti-paths.inc | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/recipes-ti/includes/ti-paths.inc b/recipes-ti/includes/ti-paths.inc
> >> index 511b5ae..5c9b716 100644
> >> --- a/recipes-ti/includes/ti-paths.inc
> >> +++ b/recipes-ti/includes/ti-paths.inc
> >> @@ -1,5 +1,6 @@
> >> installdir = "${datadir}/ti"
> >>
> >> +export TOOLCHAIN_PATH = "${STAGING_DIR_NATIVE}${prefix_native}/bin/${TARGET_SYS}"
> >> # This is where do_install will put it
> >> export AUDIO_SOC_INSTALL_DIR_RECIPE = "${installdir}/ti-audio-soc-example-tree"
> >> export BIOS_INSTALL_DIR_RECIPE = "${installdir}/ti-dspbios-tree"
> >> --
> >> 1.8.3.2
> >>
> >> --
> >> _______________________________________________
> >> meta-ti mailing list
> >> meta-ti@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2014-06-23 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 22:34 [PATCH 1/6] Remove deprecated update-modules from recipes Ash Charles
2014-06-13 22:34 ` [PATCH 2/6] Set ${TOOLCHAIN_PATH} used by some recipes Ash Charles
2014-06-23 22:05 ` Denys Dmytriyenko
2014-06-23 22:30 ` Ash Charles
2014-06-23 22:33 ` Denys Dmytriyenko [this message]
2014-06-23 23:02 ` Ash Charles
2014-06-27 19:03 ` [Patch v2] Conditionally set " Ash Charles
2014-06-13 22:34 ` [PATCH 3/6] gstreamer-ti: Break packages into dev and staticdev Ash Charles
2014-06-13 22:34 ` [PATCH 4/6] gstreamer-ti: Revert to build in place ${B} = ${S} Ash Charles
2014-06-13 22:34 ` [PATCH 5/6] Use INSANE_SKIP_${PN} = "installed-vs-shipped" Ash Charles
2014-06-13 22:34 ` [PATCH 6/6] ti-dmai: Allow do_prepsources to run release.sh Ash Charles
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=20140623223333.GL6700@edge \
--to=denys@ti.com \
--cc=ashcharles@gmail.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.