From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Boccassi Subject: Re: [PATCH v6 1/1] ci: Introduce travis builds for github repositories Date: Wed, 20 Mar 2019 21:11:07 +0000 Message-ID: References: <20190207220114.8020-1-msantana@redhat.com> <20190304161232.5670-1-msantana@redhat.com> <20190304161232.5670-2-msantana@redhat.com> <9486436.3HrUK5duha@xps> <8cc57d73-bb0e-7f42-aa45-ffc5ab6abbf7@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org, Bruce Richardson , Honnappa Nagarahalli To: msantana@redhat.com, Thomas Monjalon , Aaron Conole Return-path: Received: from mail-wr1-f67.google.com (mail-wr1-f67.google.com [209.85.221.67]) by dpdk.org (Postfix) with ESMTP id CDF571B29A for ; Wed, 20 Mar 2019 22:11:09 +0100 (CET) Received: by mail-wr1-f67.google.com with SMTP id q1so4393735wrp.0 for ; Wed, 20 Mar 2019 14:11:09 -0700 (PDT) In-Reply-To: <8cc57d73-bb0e-7f42-aa45-ffc5ab6abbf7@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 2019-03-20 at 15:28 -0400, Michael Santana Francisco wrote: > > > +matrix: > > > + include: > > > + - env: DEF_LIB=3D"static" OPTS=3D"-Denable_kmods=3Dfalse" AARCH64= =3D1 > > > + compiler: gcc > > > + addons: > > > + apt: > > > + packages: > > > + - [libnuma-dev, linux-headers-$(uname -r), python3- > > > setuptools, python3-wheel, python3-pip, ninja-build] > > > + - [gcc-aarch64-linux-gnu, libc6-dev-arm64-cross] > > Why packages are repeated here again? > > (sorry, I don't know Travis and I want to understand) > Yeah, we don't want to repeat ourselves either but we have no > choice.=20 > This is due to a limitation in travis. > This matrix does not inherit any packages from the main package list > way=20 > above, which means we have to list them out manually here. > In addition to the required packages we also want to install full > builds=20 > with libraries like libbsd-dev, libpcap-dev, etc. > We could of just put those libraries in the main package list above > and=20 > put all the builds in the env: list because then the libraries would > be=20 > inherited. > The problem with that is that is that travis would not keep minimal=20 > builds and full builds separate. > We could not have minimal builds because the minimal builds will > also=20 > inherit the additional libraries; Meson will then automatically > detect=20 > those additional libraries and builds with them. > What we would like to have is a way to tell meson which libraries we=20 > want to use and which we dont, instead of being auto-detected. This=20 > would help us to get rid of this matrix. >=20 > If someone knows a better way to do this we would greatly take in > your=20 > ideas, but so far this is the best we could come up with It's yaml so you can write the list to a variable once and reference it multiple times for brevity, see for example: https://github.com/zeromq/czmq/blob/master/.travis.yml#L128 --=20 Kind regards, Luca Boccassi