Am 25.12.21 um 21:58 schrieb Konrad Weihmann:
On 25.12.21 20:32, Stefan Herbrechtsmeier wrote:
Isn't the circular dependencies problem mainly a problem of the native
packages? In many cases the dependency only exists at compile time of
the main project and not at compile time of the dependency itself. In
case of a native package all dependency sysroots need to be finished
before the recipe sysroot itself.
Unfortunately it is not - it's happens that the go.mod already creates
this circular dependency.
The classic example is that golang.org/x/tools depends on parts of
golang.org/x/text (and guess what) golang.org/x/text depends solely on
golang.org/x/tools :facepalm:
Does this circular dependency exists in the executables (main) only?
For go itself this isn't a big issue, as the compiler just pulls all the
needed code into the compile workspace and build a binary out of it,
which can be reused later on.
But for bitbake it's a big issue, as either you pull in
golang.org/x/text + golang.org/x/tools sources into the
golang.org/x/text workspace, stripping you off the possibility to
properly watch the revision of golang.org/x/tools (in terms of devtools
and co) - or you simply end up with a circular dependency.
I scratched my head on this one for weeks, till I found a way to
actually use the latest greatest of each go module each coming as a
recipe of its own, while avoiding above mentioned situations -- and it's
kind of a huge break to how things are done right now.
I'm pretty sure the same will happen in rust sooner or later.
And I personally don't see how to break it as I don't know any way go
distinguishes between compile and runtime dependency - afaik they all
need to be present at compile time
Is it possible to create a recipe for the source and a recipe for the
binaries which depends on the source recipe? In this case the DEPENDS is
always the source package and the RDEPENDS the binary package. A
BBCLASSEXTEND could be used to create the source recipe automatically.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#160020):
https://lists.openembedded.org/g/openembedded-core/message/160020
Mute This Topic: https://lists.openembedded.org/mt/87909311/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
