On Wed, 2022-02-09 at 12:02 +0100, [email protected] wrote:
> Hello Vyacheslav and Richard,
> 
> thank you both for your feedback,
> 
> On Mon, 2022-02-08 at 10:44, Vyacheslav Yurkov wrote:
> > Any reason you set SDK to be read-only? Perhaps your use case can be covered
> > by extensible SDK? I mean if you have some shared libraries between project,
> > isn't that enough to extend your SDK to solve the original problem?
> 
> While we indeed do have shared libraries between projects, they are not
> necessary of the same version. In general we don't want to enforce 
> restrictions
> on shared code between the projects (e.g. hinder different patch sets or
> enforce specific versions), appart from the base distribution that is 
> generated
> with OpenEmbedded. If libraries mature enough that they can be considered to 
> be
> (mostly) stable, we have different processes to share it between projects.
> 
> On Mon, 2022-02-08 at 14:22, Richard Purdie wrote:
> > We definitely don't support that usage scenario since it would be highly 
> > build
> > system specific and would work in some cases but not others. I do have a
> > suggestion of a different approach though.
> 
> After your first reply, I've expected this. The Bug report #14703 can then 
> also
> be closed, however I can only set it to RESOLVED and not something like
> REJECTED, hence I would asked somebody else to reject the report.

I've marked it as "resolved WONTFIX" and added a comment summarising the
discussion here.

> 
> > Have you considered creating a sysroot per project with a copy of the 
> > sysroot
> > files?
> > 
> > This sounds like a crazy idea at first but with hardlinks for the files it 
> > is
> > fast and efficient to create these sysroot file trees. This is exactly what
> > OpenEmbedded does internally and how we handle this in our builds.
> 
> That sounds like an interesting alternative solution. We haven't thought about
> it yet, but it will be something we're going to look into.

I think/hope it should solve your probably and give you a relatively powerful
solution that isn't cmake specific.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161609): 
https://lists.openembedded.org/g/openembedded-core/message/161609
Mute This Topic: https://lists.openembedded.org/mt/88743247/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to