> On Jan 7, 2016, at 10:01 AM, Trevor Woerner wrote:
>
>
>
> On 01/07/16 11:37, Richard Purdie wrote:
>> On Thu, 2016-01-07 at 15:46 +, Burton, Ross wrote:
>>> On 7 January 2016 at 15:40, Trevor Woerner
>>> wrote:
I was surprised to find that BUILD_CC is being set to whatever
co
On Thu, 2016-01-07 at 15:46 +, Burton, Ross wrote:
>
> On 7 January 2016 at 15:40, Trevor Woerner
> wrote:
> > I was surprised to find that BUILD_CC is being set to whatever
> > comes up
> > first in our build computer's PATH. But I guess the alternative
> > would be
> > to make our builds lo
On 7 January 2016 at 15:40, Trevor Woerner wrote:
> I was surprised to find that BUILD_CC is being set to whatever comes up
> first in our build computer's PATH. But I guess the alternative would be
> to make our builds longer by compiling our own native compiler for such
> cases.
>
You could al
On 01/07/2016 01:21 PM, Trevor Woerner wrote:
If a recipe needs to build some tool on the build machine which it later
wants to invoke, my understanding is that BUILD_CC should be used?
Yes, you're right, use ${BUILD_CC}.
// Robert
--
___
Opene
If a recipe needs to build some tool on the build machine which it later
wants to invoke, my understanding is that BUILD_CC should be used?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailm
