[Bf-committers] python32_d.dll requires MSVC9
To be able to compile Blender using MSVC 2010 (x86 at least) without recompilling some of the libraries you need to disable: - Openexr - Opencollada And this is for non debug builds. This way Blender builds and is quite stable when compilled with MSVC 2010. Is possible to compile Blender using MSVC 2010 with all the features enabled, but this require you manually recompille using MSVC 2010: - Python - Openexr - OpenCollada - Zlib (for x86 only, x64 will build fine) And manually replace these on the LIB directory, or modify the cmake scripts and filelists for the linking phase. Scons will build only if you replace the old libraries in the LIB folder for the new libraries, since scons is still not updated to support MSVC 2010 (x86) and/or MSVC 2010+Windows 7 x64 SDK (for x64 builds), and will use the components taken from the environment assuming that MSVC 2008 is installed. And if you want to build cycles, you really need to recompile all it's dependencies. Good Luck with Boost ;). I've uploading builds done with MSVC 2010 to graphicall in the past, but Real Life (TM) issues keeps me to do anything serious nowadays. Maybe in the future i will upload again these, but don't hold your breath for now. Regards. J. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] python32_d.dll requires MSVC9
Sorry, is not really needed to recompile Python in the "release" builds, but only on "debug" builds. Regards J. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender on the Mac App Store
From the Mac App Store Terms and conditions: "Programs that don’t comply with Apple’s Human Interface Guidelines will not be accepted." Blender uses its own HIG. From the Adium Mailing list: "In the current agreement for the App Store - on all platforms - there are several provisions which restrict distribution. These are incompatible with the GPL. If we were to submit Adium to the App Store, any contributor - which includes contributors to underlying libraries like libpurple, libglib, or libintl - could (1) sue us directly and (2) activate the deauthorization provision in the GPL to remove our right to use the code, both because we would have knowingly violated the GPL." This was checked with Karen Sandler, which is their legal representative. These are the 2 main reasons Blender can't use the Mac App Store. Of course the Blender Foundation can ask Apple but is a well known fact that Apple dislike the GPL, and i know at least that the ffmpeg/libav guys are pretty willing to fight anyone that uses their code in any way that breaks the GPL/LGPL part of their licensed code. Can of worms, anyone? Regards. J. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender on the Mac App Store
>>They use at least bash, wget and gcc. Lets tell GNU so they can sue them! :) Apple complies publishing the modified source code of these applications indenpendently, but not xcode wich is propietary. Also apple is sponsoring BSD licensed replacements for all GPL applications used and in use currently, the most notory being LLVM and CLANG, so they are trying to get rid of all GPL code from OSX. >>I've got another idea (then I stop spamming here): >>Would it comply to App Store rules if one would write a native OS X >>application (conforming to HIG >>and BSD licensed) that is a "Blender Downloader" or "Blender Installer" or >>"Blender Manager". This >>would not include blender, but would download and install blender. It would >>also provide a menu with >>options like "put blender into dock" and "associate .blend files with >>blender" etc. Maybe it could >>let you manage multiple blender installation. E.g. blender 2.49, blender 2.5x >>and a list of the >>latest GraphicAll builds. >From the Mac App Store Terms and Conditions: "Apps that download other standalone apps will be rejected. Apps that install kexts (kernel extensions) will be rejected. Apps that require license keys or implement their own copy protection will be rejected. Apps that present a license screen at launch will be rejected. Apps may not use update mechanisms outside of the App Store." So will be rejected on the spot. >>If I would use OS X I would write such a software just to see whether Apple >>rejects it. They will. Anyways let stop polluting the mailing list about this. I think the forums of BA are the best place to discuss such things, and better, READ the terms and conditions imposed by Apple. All answers are there in plain english and very little legalesse to deal with. Regards J. >> -panzi ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] 2008 vs 2010
No real benefits, AFAIK. There's no speed benefits for using it, and no differences i've found so far. The only benefit is that you can use the express edition of msvc 2010 with the windows 7 x64 SDK to produce x64 versions of Blender for windows for free, but with some pitfalls (require recompilling some libraries) and the binary resulting is not 100% compatible with windows xp x64 (2008 was the last edition compatible with xp 64). You can't do that with the express 2008 edition without resoring to hacks. (that includes editing some registry values), and use and older SDK for windows 7. That is. J. From: Yousef Hurfoush <ba...@msn.com> To: blender foundation committers <bf-committers@blender.org> Sent: Saturday, August 20, 2011 1:24 PM Subject: [Bf-committers] 2008 vs 2010 i was just wondering what benefits give us compiling blender in vc 2010 vs 2008, is it faster? ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Back port for a possible 2.70a
Hi, Just in case a 2.70a version will be created I'm interested in this commit: GHOST: cover now both win and osx case for T39153 (commit 3600622) Complete Hash: 36006220c31b2cf5c49c126b89ddc11c024451d2 Case T39153 is quite evident if someone has a multi-monitor setup with different resolution on each monitor. So It will be reported again for sure. It was reported and fixed on time, but I didn’t know that I had to ask for a backport, my fault. Greetings, Arturo. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Revisions for the 2.70a release
Hi Sergey, I want revision with hash: 3600622 to be added. It’s a modification to the bug fix done in revision: b7712a7 to be win/mac friendly. Greetings, Arturo. El 25/03/2014, a las 16:53, Sergey Sharybin escribió: > Hey, > > Still don't really think doing 2.71 a correction release is a good idea, > too much quite WIP things in the code atm anyway. So thinking of rather > doing 'a' release. > > Here's the page with the revisions which i consider to be back ported to > the 'a' release: > http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.70/Bug_Fixes#Fixes_since_2.70_release > > Please don't modify it directly, rather poke me to add/remove stuff in > there. > > -- > With best regards, Sergey Sharybin > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Revisions for the 2.70a release
Hi Sergey, I seem not to find revision with hash: 3600622 (win/mac friendly fix to the bugfix in revision: b7712a7). So, I will add: 3600622 b7712a7 (if needed to apply 3600622) Sorry to repeat this, but the bug fixed there is really disturbing for me every time I open blender, so I will appreciate those fixes. Thanks! Arturo. El 04/04/2014, a las 09:34, Sergey Sharybin escribió: > Hi, > > Updated the list of revisions: > http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.70/Bug_Fixes#Fixes_since_2.70_release > > Please go over this list and check whether there's something which > shouldn't go or something is missing there. > > > On Wed, Mar 26, 2014 at 10:51 AM, Sergey Sharybin wrote: > >> Dan, it is expected to work and works for branches here. If you've got >> exact steps how to reproduce the issue please report a bug. >> >> Arturo, i'll add it next time i review upcoming pile of commits. >> >> But please keep this thread clear from stuff which is NOT related on 'a' >> release. >> >> >> On Wed, Mar 26, 2014 at 2:12 AM, Arturo J. Perez wrote: >> >>> Hi Sergey, >>> >>> I want revision with hash: 3600622 to be added. It's a modification to >>> the bug fix done in revision: b7712a7 to be win/mac friendly. >>> >>> Greetings, >>> >>> Arturo. >>> >>> El 25/03/2014, a las 16:53, Sergey Sharybin >>> escribió: >>> >>>> Hey, >>>> >>>> Still don't really think doing 2.71 a correction release is a good idea, >>>> too much quite WIP things in the code atm anyway. So thinking of rather >>>> doing 'a' release. >>>> >>>> Here's the page with the revisions which i consider to be back ported to >>>> the 'a' release: >>>> >>> http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.70/Bug_Fixes#Fixes_since_2.70_release >>>> >>>> Please don't modify it directly, rather poke me to add/remove stuff in >>>> there. >>>> >>>> -- >>>> With best regards, Sergey Sharybin >>>> ___ >>>> Bf-committers mailing list >>>> Bf-committers@blender.org >>>> http://lists.blender.org/mailman/listinfo/bf-committers >>> >>> ___ >>> Bf-committers mailing list >>> Bf-committers@blender.org >>> http://lists.blender.org/mailman/listinfo/bf-committers >>> >> >> >> >> -- >> With best regards, Sergey Sharybin >> > > > > -- > With best regards, Sergey Sharybin > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
[Bf-committers] Solidify --> Thickness between two concentric shells
Greetings, I am trying to pre-determine the Thickness property of the Solidify modifier required to completely fill the gap between two concentric, spherical shells. I know the diameter of both shells ahead of time, the shells will always be centered at (0,0,0). I would like to keep Offset = -1.0. Using a number of examples, I have tried to back out a mathematical relationship / equation, based on the difference in the diameter of the shells. But this falls apart when the shells diameters change, but the difference between the shell diameters remains the same. *Example: * If i have a hemisphere of diameter1 = 8m, and a smaller, concentric shell with diameter1 = 2m (difference = 6m), then a Thickness value of 0.7485 will fill the gap between these two hemispherical shells. However, if I use 2 shells that are diam1 = 100m, and diam2 = 94m (difference = 6m), then a Thickness value of 0.05975 fills in the gap between the concentric shells. How can I pre-determine what this thickness needs to be for any case of 2 concentric shells? Thank you. Aaron ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Building error with mingw in Windows7 64bit
That looks like you're just missing zlib. I don't believe that zlib is included in blender (though I am not 100% sure). Try building again after installing it. On Mon, Sep 2, 2013 at 7:27 AM, Fabio Russo wrote: > Hello to all, > I wanted to report this error: http://www.pasteall.org/45308 > SO: Windows7 64bit > Compiler: MinGW > > Best Regards, > ruesp83 > ___ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
