On Thu, Jan 7, 2021, 5:00 AM Robert Yang <[email protected]> wrote:
> Hi RP, > > On 1/7/21 6:40 PM, Richard Purdie wrote: > > 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 <[email protected]> > >>>> --- > >>>> 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. > > There are two problems to use cache-native now: > * ccache-native depends on cmake-native and zstd-native which makes it > requires > more time to build, so it might be a bottleneck for the build > > * We need disable ccache-native for about 20 native recipes to resolve the > circular dependency. > > It seems that there isn't a good way to fix the problem, or we have to > disable > ccache for native recipes, only make other recipes (cross, target and > nativesdk) > use ccache-native. > > Host's ccache isn't reliable from the history. > We had the same problem with icecream and solved it by building in a docker container with the version of ice cream that we wanted FWIW. Alternatively, I think it's possible to roll your own buildtools that has ccache? > // Robert > > > > > Cheers, > > > > Richard > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#146474): https://lists.openembedded.org/g/openembedded-core/message/146474 Mute This Topic: https://lists.openembedded.org/mt/79473091/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
