blob: 557ed10be1a8a1452f0617b530832f695ec0b919 [file] [log] [blame]
# Copyright 2014 The Chromium OS Authors. All rights reserved.
# Distributed under the terms of the GNU General Public License v2
EAPI="5"
CROS_WORKON_COMMIT="a4f1658b909e5ed64debe1da2ecc5d64e178c6f8"
CROS_WORKON_TREE="b5f25ceed86ae01cf01f49ac35d63db8077511fb"
CROS_WORKON_PROJECT="chromiumos/platform/ec"
CROS_WORKON_LOCALNAME="ec"
PYTHON_COMPAT=( python2_7 )
inherit cros-workon distutils-r1
DESCRIPTION="Host development utilities for Chromium OS EC"
HOMEPAGE="https://www.chromium.org/chromium-os/ec-development"
LICENSE="BSD-Google"
SLOT="0"
KEYWORDS="*"
ISUE=""
RDEPEND="
app-mobilephone/dfu-util
sys-firmware/servo-firmware
sys-apps/flashrom
chromeos-base/ec-utils
"
DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
set_board() {
# No need to be board specific, no tools below build code that is
# EC specific. bds works for forst side compilation.
export BOARD="bds"
}
src_configure() {
cros-workon_src_configure
distutils-r1_src_configure
}
src_compile() {
tc-export AR CC RANLIB
# In platform/ec Makefile, it uses "CC" to specify target chipset and
# "HOSTCC" to compile the utility program because it assumes developers
# want to run the utility from same host (build machine).
# In this ebuild file, we only build utility
# and we may want to build it so it can
# be executed on target devices (i.e., arm/x86/amd64), not the build
# host (BUILDCC, amd64). So we need to override HOSTCC by target "CC".
export HOSTCC="${CC}"
set_board
emake utils-host
distutils-r1_src_compile
}
src_install() {
set_board
dobin "build/${BOARD}/util/stm32mon"
dobin "build/${BOARD}/util/ec_parse_panicinfo"
dobin "util/flash_ec"
insinto /usr/bin/lib
doins util/openocd/*
distutils-r1_src_install
}