[Bf-committers] Windows platform things to do before 2.73

[Martijn Berger]

Even better reference:

http://msdn.microsoft.com/en-us/library/6sfk977f.aspx

"Provides links to environment variables used in the OpenMP API.

The Visual C++ implementation of the OpenMP standard includes the following
environment variables. These environment variables are read at program
startup and modifications to their values are ignored at runtime "



But all of this is moving away from the core issue. What do we do when we
detect either of the following:

1) System is below our minimally defined spec.

2) System has some property / setting that makes the blender experience
sub-optimal ( ancient driver / wrong system setting.

I think in the case of (1) we should fail with a user visible warning,
preferably better then just a dump to stderr at least on windows.

In the case of (2) it would be great to have some way of alerting the user
to this ( think like the reload untrusted warning )

Blender is perfectly usable without changing the OPENMP setting but it has
high cpu use in sculpting.  I think if we could warn and maybe have a fix
it button for the warning we could go without having the launcher.


Martijn






On Tue, Nov 25, 2014 at 9:26 PM, Campbell Barton <ideasman42 at gmail.com>
wrote:

> On Tue, Nov 25, 2014 at 9:16 PM, Martijn Berger
> <martijn.berger at gmail.com> wrote:
> > On Tue, Nov 25, 2014 at 6:57 PM, Sybren A. Stüvel <sybren at stuvel.eu>
> wrote:
> >
> >>
> >> Hi all,
> >>
> >> Sorry, my previous mail was sent out too quickly.
> >>
> >> On Tue, Nov 25, 2014 at 02:49:15PM +0100, Martijn Berger wrote:
> >> > - getting rid of the launcher.
> >> >   On windows we have a binary launcher that exists only to set an
> >> >   OPENMP related environment variable.
> >> >   I would like to get rid of this again in favour of setting it in
> >> >   the short-cut or setting the variable globally during install.
> >> >   Also we could and should check for this in the "System Info".
> >>
> >> What's the reason this environment variable needs to be set before the
> >> .exe is run? Can't we set it from the Blender process itself?
> >>
> >
> > This was the first thing we tried but the variable needs to be set when
> the
> > dll is loaded.
>
> It seems not,
> For reference, we had the same trouble with `PYTHONENCODING`,
> - http://bugs.python.org/msg171938
> - https://developer.blender.org/T31555
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>