964a4a9501
This allows us to create a base container with just debian packages installed, which we can pin as we uprev other parts of the dev container (e.g. rust toolchains). This prevents a frequent annoyance that new debian testing packages introduce new problems into the build infra. To make this happen, the setup scripts have been split and moved to tools/deps, with shorthands in tools/setup*. BUG=b:382504192 TEST=presubmit with new container TEST=tools/setup* on local workstation Change-Id: I0561378c76a1de026c895dfd4052ced02cb3fe8e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6153816 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
16 lines
580 B
Bash
Executable file
16 lines
580 B
Bash
Executable file
#!/usr/bin/env bash
|
|
# Copyright 2025 The ChromiumOS Authors
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
# found in the LICENSE file.
|
|
set -ex
|
|
|
|
$(dirname $0)/deps/install-x86_64-debs
|
|
$(dirname $0)/deps/install-x86_64-other
|
|
|
|
Red='\033[0;31m'
|
|
Reset='\033[0m'
|
|
# Check if submodules were initialized. If a submodule is not initialized, git
|
|
# submodule status will be prefixed with `-`
|
|
if git submodule status | grep '^-'; then
|
|
echo >&2 -e "${Red}ERROR${Reset}: Git modules were not initialized. Run 'git submodule update --init' to initialize them."
|
|
fi
|