On Thu, 2021-01-07 at 10:44 +0800, Robert Yang wrote: > Hi RP, > > On 1/6/21 9:56 PM, Richard Purdie wrote: > > On Wed, 2021-01-06 at 04:09 -0800, Robert Yang wrote: > > > Add it to buildtools-tarball so that there will be a unify version of > > > ccache, > > > which can help avoid various compile errors. > > > > > > Signed-off-by: Robert Yang <liezhi.y...@windriver.com> > > > --- > > > meta/recipes-core/meta/buildtools-tarball.bb | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/meta/recipes-core/meta/buildtools-tarball.bb > > > b/meta/recipes-core/meta/buildtools-tarball.bb > > > index 9da81d55235..2ffdd7c7253 100644 > > > --- a/meta/recipes-core/meta/buildtools-tarball.bb > > > +++ b/meta/recipes-core/meta/buildtools-tarball.bb > > > @@ -29,6 +29,7 @@ TOOLCHAIN_HOST_TASK ?= "\ > > > nativesdk-rpcsvc-proto \ > > > nativesdk-patch \ > > > nativesdk-mtools \ > > > + nativesdk-ccache \ > > > " > > > > My view is we should not start to ship ccache with buildtools by > > default. Its something that the user can install if they want/need it > > > The problem is that user installed ccache may not work with our recipes, for > example, we found the following recipes failed to build with ccache on > different > hosts: > > cdrtools-native > fribidi > rocksdb > > > So have a fixed version of ccache can make sure the recipes work well, it > also > helps us to reproduce the errors easily when user reported a bug.
I really do not want ccache in buildtools. If this is such a problem, we need to work out how to resolve the circular dependency issues so ccache-native can work again. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#146468): https://lists.openembedded.org/g/openembedded-core/message/146468 Mute This Topic: https://lists.openembedded.org/mt/79473091/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
