Re: [Bf-committers] Blender 2.8 planning notes 2017-07-24

2017-07-25 Thread Mike Erwin
On Mon, Jul 24, 2017 at 8:31 AM, Campbell Barton wrote: > > > Meeting agrees we don't like to do planning behind closed-doors and to > to move future meetings into #blendercoders > So others can more easily be involved in 2.8x development. > Yes!!! An open development process is one of our greate

Re: [Bf-committers] Blender dependencies scripts in main repo

2017-07-25 Thread Ray Molenkamp
On 7/25/2017 3:38 AM, Sergey Sharybin wrote: > >> I would like to have the files in the main Blender repo so that when adding >> or upgrading a library, a single commit documents all the changes, and can >> be submitted to differential. It also means we can reuse existing cmake >> code, which is

Re: [Bf-committers] Blender dependencies scripts in main repo

2017-07-25 Thread Sergey Sharybin
Perhaps what we really need is some dedicated file which lists exact library versions we need for a proper Blender release, which is used by whatever build/install/testing system is used on various platforms. This way: 1. We will have version of libraries stored in Git. Not sure history is really

Re: [Bf-committers] Blender dependencies scripts in main repo

2017-07-25 Thread Brecht Van Lommel
On Tue, Jul 25, 2017 at 11:38 AM, Sergey Sharybin wrote: > Ideally you need to tell the builder script which library you want to > (re)build. Exposing all this to Blender's makefile/make.bat could cause too > much noise in Blender's sources. It could use the WITH_* flags to determine which libr

Re: [Bf-committers] Blender dependencies scripts in main repo

2017-07-25 Thread Sergey Sharybin
Hi, Answers are inlined. On Tue, Jul 25, 2017 at 11:15 AM, Brecht Van Lommel < brechtvanlom...@pandora.be> wrote: > I don't think we want users to build their own libraries on Windows and > macOS, so we wouldn't advertise this in the build docs. The option can be > made a bit more hidden if need

Re: [Bf-committers] Blender dependencies scripts in main repo

2017-07-25 Thread Brecht Van Lommel
I don't think we want users to build their own libraries on Windows and macOS, so we wouldn't advertise this in the build docs. The option can be made a bit more hidden if needed. For install_deps.sh, in my personal opinion reusing as many packages from the system as possible is rather pointless.