From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 5551FE00B51; Wed, 31 May 2017 09:22:19 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [134.134.136.100 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DFE39E00992 for ; Wed, 31 May 2017 09:22:16 -0700 (PDT) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga105.jf.intel.com with ESMTP; 31 May 2017 09:22:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,275,1493708400"; d="scan'208,217";a="109245559" Received: from jlock-mobl1.ger.corp.intel.com ([10.252.13.172]) by fmsmga006.fm.intel.com with ESMTP; 31 May 2017 09:21:52 -0700 Message-ID: <1496247706.8526.14.camel@linux.intel.com> From: Joshua Lock To: Alain Achkar , pidge@toganlabs.com Date: Wed, 31 May 2017 17:21:46 +0100 In-Reply-To: References: <1478889473.18810.3.camel@toganlabs.com> X-Mailer: Evolution 3.22.6 (3.22.6-2.fc25) Mime-Version: 1.0 Cc: yocto@yoctoproject.org Subject: Re: Buildbot / Autobuilder / custom? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 16:22:19 -0000 Content-Type: multipart/alternative; boundary="=-6RkGgH+H7NzjuW6bP3IL" --=-6RkGgH+H7NzjuW6bP3IL Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Mon, 2017-05-29 at 17:01 -0400, Alain Achkar wrote: > Hello Beth and/or Joshua, > I would really appreciate some pointers on how to get the Variscite > builds to work with Autobuilder. > > Since my last email, I was able to setup the Yocto Autobuilder, add > the sample hello.conf and run it. > I was also able to add another file, nightly-variscite-x11.conf and I > can see it in the Waterfall view. Initially, I started by filling it > with content similar to hello.conf and this worked. Now, I need to be > able to add the Variscite build. > > Since my last email, Variscite have moved to the morty branch, since > Freescale/NXP have moved to the morty branch. So, the wiki > instructions here http://variwiki.com/index.php?title=Yocto_Build_Rel > ease&release=RELEASE_MORTY_BETA_DART-6UL are now simpler: > > 1) Checkout the source code > $ mkdir ~/var-fslc-yocto > $ cd ~/var-fslc-yocto > $ repo init -u https://github.com/varigit/variscite-bsp-platform.git > -b morty > $ repo sync -j4 > > 2) Run the setup script (which calls oe-init-environment) > $ cd ~/var-fslc-yocto > $ MACHINE=imx6ul-var-dart DISTRO=fslc-x11 . setup-environment > build_x11 > > 3) Build X11 demo images > # Without Qt content: > $ bitbake fsl-image-gui > > # Or with Qt content: > $ bitbake fsl-image-qt5 > > The 'repo' command reads the file default.xml which has the following > contents: > > > > > >   > > >   >   >   >   >   >   > > >   revision="6a1f33cc40bfac33cf030fe41e1a8efd1e5fad6f" upstream="morty" >  name="poky" path="sources/poky"/> >   revision="56a1460777d1e24b1dfb426cad2b103740936a83" upstream="morty" >  name="meta-freescale" path="sources/meta-freescale" /> > > >   revision="fe5c83312de11e80b85680ef237f8acb04b4b26e" upstream="morty" > name="meta-openembedded" path="sources/meta-openembedded" /> > > >   > > >   > > >   revision="4be3db25959e741ac9164a32c82b8c09b59213ad" upstream="morty" > name="meta-freescale-3rdparty" path="sources/meta-freescale- > 3rdparty"/> >   revision="dd482aeb7913c099c69f82362776bd92b584553c" upstream="morty" > name="meta-freescale-distro" path="sources/meta-freescale-distro"/> >   revision="3601fd2c5306ac6d5d0d536e0be8cbb90da9b4c1" upstream="morty" > name="meta-qt5" path="sources/meta-qt5"/> >   revision="7d37ae2adec5cc5ea27367ce125bc7bce2310ca1" upstream="morty" > name="meta-browser" path="sources/meta-browser"/> >   revision="7a214e7579869be810aa8992c59627ba064db076" upstream="morty" > name="meta-variscite-fslc" path="sources/meta-variscite-fslc"  /> > > > > > > > So, AFAIK, I need to either (a) translate these into the 'repos' > property in my buildset, or write a custom buildstep that can use the > 'repo' tool to clone the needed repositories. You are correct. The other step you might have issues with is the setup environment script, yocto-autobuilder currently expects to source oe-init-build-env and doesn't support other init scripts presently. I have a WIP patch to support alternative environment scripts, but it doesn't fully resolve support for your BSP as it seems from the example above that MACHINE and DISTRO need to be set in the environment when the script is sourced. Will those values be picked up from auto.conf if not set in the environment? Joshua --=-6RkGgH+H7NzjuW6bP3IL Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
On Mon, 2017-05-29 at 17:01 -0400, Alain Achk= ar wrote:
Hello Beth and/or= Joshua,

I would really appreciate some pointers on how = to get the Variscite builds to work with Autobuilder.

<= div>Since my last email, I was able to setup the Yocto Autobuilder, add the= sample hello.conf and run it.
I was also able to add another fil= e, nightly-variscite-x11.conf and I can see it in the Waterfall view. Initi= ally, I started by filling it with content similar to hello.conf and this w= orked. Now, I need to be able to add the Variscite build.

Since my last email, Variscite have moved to the morty branch, sinc= e Freescale/NXP have moved to the morty branch. So, the wiki instructions h= ere http://variwiki.com/index.php?titl= e=3DYocto_Build_Release&release=3DRELEASE_MORTY_BETA_DART-6UL are n= ow simpler:

1) Checkout the source code
= 
$ mkdir ~/var-fslc-yocto
$ cd ~/var-fslc-yocto
$ repo init -u https://gi=
thub.com/varigit/variscite-bsp-platform.git -b morty
$ repo sync -j4

2) Run the setup script (whi= ch calls oe-init-environment)
$ cd ~/var-fslc-yocto
$ MACHINE=3Dimx6ul-var-dart DISTRO=3Dfslc-x11 . setup-environment build_x11=

3) Build X11 demo images
# Wi=
thout Qt content:
$ bitbake fsl-image-gui

# Or with Qt content:
$ bitbake fsl-image-qt5

The 'repo' command r= eads the file default.xml which has the following contents:
= 
<?xml version=3D"1.0" encoding=3D=
"UTF-8"?>
<manif=
est>

  <default sync-j=3D"4"=
 revision=3D"morty"/>

  <rem=
ote fetch=3D"https://git.yocto=
project.org/git" name=3D"yocto"/>
  <remote fetch=3D"https://github.com/Freescale"     name=3D"freesca=
le"/>
  <re=
mote fetch=3D"https://github.co=
m/openembedded"  name=3D"oe"/>
  <remote fetch=3D"https://github.com/varigit"       name=3D"va=
riscite"/>
  &=
lt;remote fetch=3D"https://github.=
com/OSSystems"     name=3D"OSSystems"/>
<=
font face=3D"monospace, monospace">  <remote fetch=3D"git://github.com/meta-qt5"     &nbs=
p;  name=3D"QT5"/>

  <p=
roject remote=3D"yocto" revision=3D"6a1f33cc40bfac33cf030fe41e1a8efd1e5fad6=
f" upstream=3D"morty"  name=3D"poky" path=3D"sources/poky"/>=

  <project remote=3D=
"yocto" revision=3D"56a1460777d1e24b1dfb426cad2b103740936a83" upstream=3D"m=
orty"  name=3D"meta-freescale" path=3D"sources/meta-freescale" />

<=
font face=3D"monospace, monospace">  <project remote=3D"oe" revisio=
n=3D"fe5c83312de11e80b85680ef237f8acb04b4b26e" upstream=3D"morty" name=3D"m=
eta-openembedded" path=3D"sources/meta-openembedded" />

  <project remote=3D"variscite" revision=3D"mor=
ty" name=3D"variscite-bsp-base" path=3D"sources/base">
=
	<copyfile dest=3D"README" src=3D"README"=
/>
	<copyfile dest=3D=
"setup-environment" src=3D"setup-environment"/>
  </project>

  <project remote=3D"freescale" revision=3D"4be3db259=
59e741ac9164a32c82b8c09b59213ad" upstream=3D"morty" name=3D"meta-freescale-=
3rdparty" path=3D"sources/meta-freescale-3rdparty"/>
  <project remote=3D"freescale" r=
evision=3D"dd482aeb7913c099c69f82362776bd92b584553c" upstream=3D"morty" nam=
e=3D"meta-freescale-distro" path=3D"sources/meta-freescale-distro"/>
  <project remote=
=3D"QT5" revision=3D"3601fd2c5306ac6d5d0d536e0be8cbb90da9b4c1" upstream=3D"=
morty" name=3D"meta-qt5" path=3D"sources/meta-qt5"/>
  <project remote=3D"OSSystems" r=
evision=3D"7d37ae2adec5cc5ea27367ce125bc7bce2310ca1" upstream=3D"morty" nam=
e=3D"meta-browser" path=3D"sources/meta-browser"/>
  <project remote=3D"variscite" rev=
ision=3D"7a214e7579869be810aa8992c59627ba064db076" upstream=3D"morty" name=
=3D"meta-variscite-fslc" path=3D"sources/meta-variscite-fslc"  />

<=
font face=3D"monospace, monospace"></manifest>


So, AFA= IK, I need to either (a) translate these into the 'repos' property in my bu= ildset, or write a custom buildstep that can use the 'repo' tool to clone t= he needed repositories.

You are correct.

The other step you might have = issues with is the setup environment script, yocto-autobuilder currently ex= pects to source oe-init-build-env and doesn't support other init scripts pr= esently.

I have a WIP patch to support alternative= environment scripts, but it doesn't fully resolve support for your BSP as = it seems from the example above that MACHINE and DISTRO need to be set in t= he environment when the script is sourced.
Will those values be p= icked up from auto.conf if not set in the environment?

=
Joshua
--=-6RkGgH+H7NzjuW6bP3IL--