> That said, I'm ok with making perfetto support a build-time option
> that is default disabled. And I think it would be even ok to limit
> use of perfetto to individual drivers (ie. no core mesa/gallium
> perfetto dependency) to start. And, well, CrOS has plenty of mesa
> contributors so I
So, I did an experiment to get a feel for how hard/easy updating
perfetto sdk would be.. I took gfx-pps (which already "vendors" the
perfetto sdk) and rebuilt it with perfetto.cc/h from each existing
perfetto release tag (v3.0 is the earliest I see, v12.1 is the
latest). I did hack out the intel
I've seen other projects successfully leveraging git submodules for including
3rd party code without vendoring in the stricter sense. I don't have direct
experience doing so myself yet, but I hope one day to move apitrace towards
this. (Apitrace bundles lots of 3rd party code, partly for
