[Mesa-dev] Is there a mesa Docker image available like on travis-ci? (was Re: [PATCH 1/2] gallium/targets/dri: Add libunwind to linker flags)

Andres Gomez agomez at igalia.com
Wed Sep 13 11:20:52 UTC 2017


On Tue, 2017-09-12 at 12:17 +0200, Gert Wollny wrote:
> > > This doesn't seem right. GALLIUM_COMMON_LIB_DEPS already has
> > > $(LIBUNWIND_LIBS) so this change should not be needed.
> > 
> > I already started looking at this, but haven't been able to figure
> > out why in this specific configuration GALLIUM_COMMON_LIB_DEPS seems
> > to be empty, or at least it doesn't add libunwind. 
> 
> I kind of hit a wall trying to figure out what's going on: On
> Debian/Stretch  I can't reproduce it and  on travis-ci enabling verbose
> output cancels the build because the output gets larger than 4MB
> (so much for --disable-silent-rules). 
> 
> Is there a docker image available that resembles the travis-ci build
> environment as it is set up in mesa/.travis.yml (i.e. Ubuntu/Trusty
> with all the manually compiled packages)?

Just mentioning in case it is helpful.

Juan and I have been using for a while a .travis.yml customized version
in which we use docker. One of the reasons is precisely to be able to
just get the image in case we want to check something there.

Our configurations are somehow different than the ones in current
.travis.yml and you will have to set some variables in Travis to enable
the build but it is pretty straight forward. Ask, in any case, if you
have problems with that.

These are the resources you would like to check:
 * https://github.com/Igalia/mesa-dockerfiles this is where we host our
   Dockerfiles (Rockerfiles, actually).
    * https://travis-ci.org/Igalia/mesa-dockerfiles
 * https://github.com/Igalia/release-mesa/tree/agomez/master this is
   current master with the patch that brings our customized .travis.yml
   applied.
    * https://travis-ci.org/Igalia/release-mesa/builds/274988548

Also, we would like to hear opinions about transitioning for a Travis
configuration in which docker images could be used. We are working in a
patch proposal but this will come a bit later ...

-- 
Br,

Andres


More information about the mesa-dev mailing list