[Bf-committers] Propose to reduce default feature set (*nix dev builds)
ideasman42 at gmail.com
Thu Nov 13 15:24:26 CET 2014
On Thu, Nov 13, 2014 at 2:05 PM, AIBlender <aiblender at gmail.com> wrote:
> On 13/11/14 11:31, Campbell Barton wrote:
>> This is mainly for Linux/BSD developers (releases remain unchanged).
>> Its getting increasingly difficult to build Blender on Linux, (LLVM,
>> ffmpeg, OpenCollada...) & these issue's can't always be fixed on our
>> With newer developers a failed build with a cryptic error message
>> (guys in #blendercoders can't even help with), is quite off putting..
>> Proposing a limited feature-set by default with CMake (again official
>> builds from blender.org are unchanged)
> This is a bad idea, the whole point on dev builds is for us to spot
it can also be for developers to start working on Blender.
> if you start turning off features just so things can compile
> that is sweeping issues under the carpet.
Buildbot's will continue to run with a complete feature set.
> If it's getting hard to build
> that means you need to work on build instructions/build system. And if
> its an upstream issue, communication needs to go upstream. Being
> demotivated if not a reason to start turning off fundamental features.
You assume this is some laziness and if we wanted we could spend time
to resolve issues like this.
We regularly get new devs in IRC who pastebin strange errors we never
saw before and its unlikely we can help them resolve.
> After all ffmpeg and opencollada would not really be seen as option
> features (by a lot of people), and the same can be said of llvm, and
> they certainly are not optional when we need to spot bug/issues.
This is just defaults, so builds are more likely to work out-of-the
box. if you know what OSL/FFMPEG/FFTW/LLVM... etc mean and need them,
you can of course enable them.
> I mean
> what is next stop supporting Linux because its harder to build. Well
> you could just as easily make that argument for the entire windows build
Windows uses pre-compiled libs, While we do have problems reported its
not normally related to using some unknown library version.
> It's more often than not the one with problems, so we should
> obviously throw it in the canal yes? Obviously that would not be done.
> *marches off all huffy like*
> Terry Wallwork
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers