If the tool is executed with a direct path in a script e.g.
#!/usr/bin/python
or the host path is hardcoded inside a binary, there's nothing you can do
(other than temporarily rename python to something else, and fix all
instances of breakage to use #!/usr/bin/env python).
If the execution
Hi all,
it maybe a already solved, very trivial thing to do, but is there any
way in bitbake to prevent that a tool from the build host is executed
instead of the same tool (maybe) available via the sysroot-native?
In shell I would typically do (e.g.) something like this
python() { echo
Hi,
Did you install the SDK?
Did you run the environment script?
make: /path/to/your/yocto/toolchain/bin/arm--linux-gnueabihf-gcc: Kommando
nicht gefunden
LEX scripts/kconfig/lexer.lex.c
/bin/sh: 1: flex: not found
YACCscripts/kconfig/parser.tab.h
/bin/sh: 1: bison: not
On 22/01/2020 17.59, Richard Purdie wrote:
> On Wed, 2020-01-22 at 16:39 +, Rasmus Villemoes wrote:
>> On 22/01/2020 16.50, Richard Purdie wrote:
>>> On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
On 22/01/2020 15.35, Richard Purdie wrote:
>>
>> I can't be the first one to
On 22/01/2020 17.39, Rasmus Villemoes via Lists.Yoctoproject.Org wrote:
> On 22/01/2020 16.50, Richard Purdie wrote:
>> On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
>>> On 22/01/2020 15.35, Richard Purdie wrote:
Bitbake can only detect direct references to variables. The code
On Wed, 2020-01-22 at 16:39 +, Rasmus Villemoes wrote:
> On 22/01/2020 16.50, Richard Purdie wrote:
> > On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
> > > On 22/01/2020 15.35, Richard Purdie wrote:
> > > > Bitbake can only detect direct references to variables. The
> > > > code
>
On 22/01/2020 16.50, Richard Purdie wrote:
> On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
>> On 22/01/2020 15.35, Richard Purdie wrote:
>>> Bitbake can only detect direct references to variables. The code
>>> above only runs at configure time, not at parse time so its not
>>> really
On Wed, 2020-01-22 at 15:46 +, Rasmus Villemoes wrote:
> On 22/01/2020 15.35, Richard Purdie wrote:
> > Bitbake can only detect direct references to variables. The code
> > above only runs at configure time, not at parse time so its not
> > really surprising that bitbake can't know what its
