On Thu, 30 May 2019 at 21:27, Serkan Türker wrote:
> I understand the process of debugging build failures. I am just confused why
> my approach doesn't work.
> "python-soundcloud.bb" has the same format like other python module recipes
> in meta-oe.
> In tizonia.bb, I have added "python-soundclo
I understand the process of debugging build failures. I am just confused
why my approach doesn't work.
"python-soundcloud.bb" has the same format like other python module recipes
in meta-oe.
In tizonia.bb, I have added "python-soundcloud" to DEPENDS, so I assumed
bitbake would resolve the necessary
I guess you could start by looking at configure.ac in the failing
component's source code and specifically which m4 macro it is using to find
the python module, then look at the definition of that macro and what it
does. Sadly, this kind of thing - working your way through large,
unfamiliar code ba
Hi Alexander,
thank you for the quick reply. Doing the ./configure part on the host
machine for host (basically, compiling tizonia on Ubuntu) works fine, there
it can find the soundcloud module. I just don't understand where autotools
(during bitbake) is looking for the soundcloud module and what
This is really an autotools question, not a yocto question. Specifically,
what happens at this point?
*| checking python module: soundcloud... no*
Quite likely, the autotools script runs native python and asks it to import
soundcloud, which fails. You need a different approach, maybe checking for
