[Bf-committers] Proposal: Building blender using docker.io

Sergey Sharybin sergey.vfx at gmail.com
Tue Apr 28 16:31:58 CEST 2015


Hi,

I don't have strong opinion about having some container-based approach next
to our current build process if it's maintained and used by reasonable
amount of users.

But i'm against making it officially suggested way to have blender compiled
locally. `this is because using blender on a real hardware and system is
what you really want as an artist. It is also more convenient for
development. If there are difficulties with making blender compiled on a
real system this is either to be addressed via documentation (HowTo Compile
section in Wiki) or adopt current install_deps script.

And one more thing -- we should not bump requirement to an external
libraries and just break compilation with older versions. Such actions will
piss everyone off regardless how they're building blender. Blender should
be kept compilable with reasonably older version of libraries comparing to
what we're using for official release (disabling some features at build
time is acceptable for this).

P.S. We can also share official release environment as a chroot or virtual
machine image for those who wants to create truly static builds.


On Tue, Apr 28, 2015 at 5:20 PM, Martijn Berger <martijn.berger at gmail.com>
wrote:

> Hi Jeroen,
>
> I think that any and all things that make blender more easy / more
> accessible to any group of people could be potentially helpful.
> And that container / *a controlled environment* is a great things when
> trying to get a better build process, that is also why the linux build of
> blender is already build this way.
> I think we should not restrict ourselves to < insert popular
> containerization solution here >, lets call it docker for now.
> https://chimeracoder.github.io/docker-without-docker/#1 is a good
> presentation about how (un)special docker is in this regard.
> I think if you ask Sergey he can provide you with a tarball of the current
> chroot used to build..
> You could just add some docker sprinkles to it and have some of your goals
> achieved.
>
> Regards,
>
> Martijn
>
>
>
>
>
>
>
>
>
> On Tue, Apr 28, 2015 at 9:49 AM, Jeroen Bakker <j.bakker at atmind.nl> wrote:
>
> > Hi all,
> >
> > I am using install_deps.sh to build blender on Linux systems. It is
> > always a tedious work to get Blender compiling again when we upgrade an
> > external library. I have solved this trick before using docker.io. the
> > last week I started experimenting on using docker.io for compiling
> > blender. I succeeded on an ubuntu 14.04 and 15.04 host.
> >
> > For now I created a proposal for this. My goal is to get more control
> > over the software versions. Help developers to stick to their task (what
> > is developing code). Make it easier for newbies to create their building
> > environment.
> >
> > For more details please read the proposal at:
> > http://wiki.blender.org/index.php/User:Jbakker/Blender_docker
> >
> > in order to get this project going:
> > * ok if this is a valid target.
> > * write documentation about using docker.io for compiling blender.
> > * write scripts (Dockerfile) to recreate blender docker images
> > * register these images in a public registry (so other users do not need
> > to compile the images themself, but can download them)
> > *  support from the community in testing.
> >
> > Regards,
> > Jeroen
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin


More information about the Bf-committers mailing list