Dockerfile: stop tracking virglrenderer master

With crrev.com/c/1745316, the regular ChromeOS build started
adding epatches to virglrenderer. Therefore, don't track virglrenderer
master for the time being, until we can upstream and/or remove our
downstream APIs.

BUG=chromium:906811
TEST=docker/wrapped_smoke_test.sh

Change-Id: I9567e9286130048fb793fecb4ff3801b7d64ddba
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1758371
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: David Riley <davidriley@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
This commit is contained in:
Gurchetan Singh 2019-08-16 09:28:28 -07:00 committed by Commit Bot
parent 99c9c685b5
commit 84d59e76b3

View file

@ -89,9 +89,11 @@ RUN git clone https://github.com/anholt/libepoxy.git \
&& meson \
&& ninja install
# virglrenderer is under heavy development on master and we want the very latest.
RUN git clone https://gitlab.freedesktop.org/virgl/virglrenderer.git \
# We've forked virglrenderer to accomodate differences in the GBM header.
# Until we can upstream our changes, build based on this downstream tree.
RUN git clone https://gitlab.freedesktop.org/gurchetansingh/virglrenderer.git \
&& cd virglrenderer \
&& git checkout keep-kokoro-happy \
&& ./autogen.sh \
&& make install -j$(nproc)