[Bf-committers] Blender issues on Windows

bjornmose at gmx.net bjornmose at gmx.net
Wed Nov 21 01:17:57 CET 2012

I voice up rarely because I use pretty aged versions of blender in our 
production line.
Building Blender for Windows  from the 'hot rod' is a challenge every 
time I try.
Most annoying is downloading the entire lib/windows mess for an/some 
hour(s) on a clean (virtual) machine.
Yes .. we do use virtual machines .. just to tame the windows version 
zoo on the customer side :)
IMHO that directory needs to be structured like
lib .. windows
      (..target switch)
          ..development system
          ..Unix clones
          ..ms likes

          ..development system
           ..Unix clones
           ..ms likes
so I can check out the things I really need
old man's grumbling ends here .. almost,
A symbolic hug at the
flying Dutchman
I know it is hard to control a pile of ants.

Am 20.11.2012 23:28, schrieb Erwin Coumans:
> An alternative to avoid huge libraries is to add cmake/scons support
>   to build BOOST from source, at least for Windows.
> Just copy the BOOST source code in blender/extern for example.
> Of course this can stay pure optional,
> so it will be ignored if you use precompiled libraries.
> On 20 November 2012 14:08, Mitchell Stokes <mogurijin at gmail.com> wrote:
>> t seems to me we almost need another lib checkout to deal with vc10,
>> similar to the mingw ones. It is rather annoying to have to download a pile
>> of Boost libs only to have to turn around and compile my own anyways. We
>> could use an svn external to handle libs that both can use (share). Also,
>> the build.bat needs modifications to build libs for vc10 (different folder
>> structure).
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list