Hi Lukas,
Sorry for the late reply.
I think I see what's going on.
The module I'm working on is already "vendored", which means there's no
modules.txt created for my project by recipetool, since it's already
provided in the repository itself.
I guess this has pros and cons, and I'm currently not sure which
approach is better. On one hand, offline vendoring (no by the
recipetool) has an advantage for SDK builds, when people don't use the
BSP directly. On the other hand, Yocto style vendoring (when modules.txt
is stored in the BSP) is more transparent for dependency management.
I.e. I would need to update the recipe when my dependencies change.
Slava
On 15.11.2023 08:34, Vyacheslav Yurkov via lists.openembedded.org wrote:
On 15.11.2023 08:30, Lukas Funke wrote:
Hi Slava,
No problem. Party is still going on. The 'modules.txt' is intendet to
be in your ${WORKDIR} as it is part of the SRC_URI, generated by
the recipetool. My guess would be, that there is some
missconfiguration in your SRC_URI?
Yes, I noticed that it should be there in recipetool tests. But
generated recipe didn't have It in SRC_URI. I tried to use generated
recipe as is. I'll try to double check later.
Slava
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193015):
https://lists.openembedded.org/g/openembedded-core/message/193015
Mute This Topic: https://lists.openembedded.org/mt/102345308/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
