Re: [Bf-committers] MinGW buildbots
Slightly off-topic here, but has the OpenMP issue been resolved with MinGW-w64 yet? If I recall correctly, there were some issues with various parts of Blender when compiled with OpenMP because of a bug on MinGW-w64's end, I was just wondering if this has been resolved? On 16/01/2015 10:06 am, "Antony Riakiotakis" wrote: Probably one of the slaves was my laptop but it's not idle enough to act as buildslave. Side note - I am preparing an upgrade to a MinGW-w64/gcc/4.9.2 seh-posix based build for our supported platform. On 16 January 2015 at 00:02, Sergey Sharybin wrote: > Hi, > > There are two mingw64 slaves which were online for quite some time now (at > least few months). > > Are they gonna to be maintained or we can hide them and stop trying to > schedule builds on them? > > -- > 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 mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Change of MinGW64 compiler
Some debugging reveals that the crash is caused by the pthreadGC2-w64.dll library that is included with the buildbot builds. I have no idea how this library made its way into the build, it is not needed for building, nor part of MinGW-w64 or the Blender mingw64 library repository. This is definitely an issue with the buildbot, not the compiler or Blender code base. On 9/07/2012 7:54 PM, Constantin Rahn wrote: > Hi, > > the current build bot mingw win64 r48748 crashes on startup. Confirmed > by JesterKing on IRC. > "jesterKing: 48700 already crashes on startup. I'm guessing it has to do > with the dlls that are now used in mingw64 builds (gomp, gcc_s_sjlj, > winpthread, stdc++-6)" > > Could this be a problem with your latest changes? > Who could fix this? Blender Developers (maybe you) or is it a problem on > the mingw side? > > Happy blending > Conz ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Change of MinGW64 compiler
It was posted on the mailing list a few weeks ago, you should be using this MinGW-w64 build: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/release/x86_64-w64-mingw32-gcc-4.7.1-release-win64_rubenvb.7z/download Make sure your libraries are up to date before compiling too, good luck :) ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Change of MinGW64 compiler
This build is the new one used by the buildbot. What issue are you having exactly? On 15/07/2012 5:16 PM, Yousef Hurfoush wrote: > i used the this build, i though nathan has another one. > the problem is still there! > > Regards > Yousef Harfoush > ba...@msn.com > ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] State of VS2012 support...
Visual Studio 2013 runs on Windows 7 and above (not Windows 8 and above), and can compile C/C++ code that runs on Windows Vista and above. Considering that Microsoft is fully dropping support for Windows XP this coming April, I think then would be an ideal time to make the switch to Visual Studio 2013. We'll be able to compile far more optimised code with the 5 years of development since 2008, be able to use C++11 features without worrying about breaking support for Windows, and developers who only have access to the free express edition of Visual Studio will be able to compile 64-bit code which is not available in the free 2008 edition. On Sun, Dec 15, 2013 at 2:37 PM, spatial wrote: > I just want to add 2 essential points to the discussion for consideration > > - visual studio 13 needs at least win8 > - visual studio 12, as far as I could check, it isn't aviable any more > > question is, if these steps wouldn't lock out too much developers > (I would be one of them...) > ___ > 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] build blender with mingw
I managed to compile Blender yesterday on MinGW-w64 with a few essential dependencies, but got an instant access violation in main(). Suspect that it's a pthread issue, but I'm not sure. GDB didn't provide much useful information. On Mar 11, 2012 8:27 AM, "Campbell Barton" wrote: > > On Sun, Mar 11, 2012 at 7:21 AM, Antony Riakiotakis wrote: > > Yes it's possible with official MinGW, not MinGW64. Make sure you use > > a 32 bit python 2.6 for scons as MinGW creates 32bit binaries. MinGW64 > > support is not yet included. It would require recompilation of almost > > every library blender is linked against which can be a daunting task > > to do. > > Its reasonable IMHO not to support all dependencies initially, > could start out with mingw64 builds only having basics - libjpeg, > libpng - and add more along the way. > The build-systems can disable all unsupported deps automatic to > prevent obscure errors, until the deps are added. > ___ > 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] build blender with mingw
http://www.mediafire.com/?gryvbqgotcv1s5q This will let Blender compile on MinGW-w64 (includes libraries) on SCons, but the resulting binary instantly crashes. If anyone wants to investigate, feel free to. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 12:27 AM, Antony Riakiotakis wrote: > Caleb, the libraries you are using are appended with .lib. I am not > sure exactly how you generated them but MinGW libraries will have a > lib*.a naming convention. Especially for C++ generated libraries we > need to get libraries generated from MinGW as the ABIs differ between > compilers. I haven't tried using your patches yet though. They were all built with MinGW-w64, I renamed them to .lib to avoid errors about the library not being found when building Blender. It was a while ago when I built OpenEXR, so I'm not sure what the issue is here. It sounds like your MSYS install is outdated, make sure you're using the one from http://code.google.com/p/msysgit/downloads/list (msysGit-fullinstall-1.7.10-preview20120409.exe). Also, try reading the MinGW build notes in the /lib/windows/openexr SVN folder, I recall some code needs patching for MinGW complication. When I got Blender to build with MinGW-w64, it instantly crashed. I traced this to a Unicode-related function in Python failing, but I don't have the debug logs any more. I originally thought this was to do with MinGW-w64's pthread implementation, but it turned out to be Python. Let us know if you have better luck. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 8:40 PM, Antony Riakiotakis wrote: > I am extremely proud to announce I have the first working build of > blender built with MinGW64:) > > The problem is with pyextensions, look athttp://bugs.python.org/issue4709 > > The solution is to define MS_WIN64 when building with MinGW64. Awesome :) Are you using the Python DLL built using Visual Studio with a .def file, or did you actually manage to build Python with MinGW-w64? I built it myself and couldn't get Python to start without some kind of error last time I tried. I'll try again if you could elaborate how you fixed the Python issue. I didn't document my process for building OpenEXR sorry, but I did use rubenvb's gcc 4.7 build. I compiled OpenEXR 1.6.1, and OpenImageIO 1.0 (think it was latest git revision) if that helps. If you don't manage to get it complied (I'm sure you will), feel free to try the libraries I built in March at http://www.mediafire.com/download.php?gryvbqgotcv1s5q . Getting stuff to compile with MinGW-w64 involves a lot of hacking along with trial and error, so I didn't bother to record my steps and modifications :P Best of luck getting it to build, can't wait to see how much faster Cycles will be. I'll try again when I get some time and figure Python out. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 9:37 PM, Antony Riakiotakis wrote: > Hi, using the def generated and adding a definition through the > CMakefile did it for me. I am sure if you add a define through the > mingw64 configuration file it will work Cool, didn't realise it was that simple. Compiling now, I'll let you know how it goes. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 9:37 PM, Antony Riakiotakis wrote: > Hi, using the def generated and adding a definition through the > CMakefile did it for me. I am sure if you add a define through the > mingw64 configuration file it will work Hooray! I can confirm adding -DMS_WIN64 to the preprocessor flags lets Blender run perfectly! Thanks for figuring that out :) The speed differences are amazing. On the same scene with Cycles, the Visual Studio build takes 1min 33.15sec to render, while the MinGW-w64 build (built with -O3 and -march=nocona) only takes 48.62sec. This is 95% faster, almost double the speed! Perhaps we should aim at getting this in trunk somehow? ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 10:25 PM, Caleb Joseph wrote: > The speed differences are amazing. On the same scene with Cycles, the > Visual Studio build takes 1min 33.15sec to render, while the MinGW-w64 > build (built with -O3 and -march=nocona) only takes 48.62sec. This is > 95% faster, almost double the speed! I should also note the two renders match each other pixel perfect, meaning there are no weird math optimisation bugs. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] build blender with mingw
On 22/04/2012 10:27 PM, Antony Riakiotakis wrote: > Yes, I will ask on this meeting:). > > Thanks for confirming! Currently the only libraries that need to be sorted out on my system are FFmpeg and SDL which give linking errors, gettext and iconv which need compiling, and Collada which also needs compiling. Everything else set by default in a 32-bit MinGW build I was able to get working. How is it looking on your build environment? ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] trying to build with mingw32
On 25/04/2012 2:36 PM, Yousef Hurfoush wrote: > scons: done reading SConscript files. > scons: Building targets ... > Compiling ==> 'avi.c' > scons: *** > [Z:\Development\blender\build\win32-mingw\source\blender\avi\intern\a > vi.o] The system cannot find the file specified > scons: building terminated because of errors. Looks like MinGW isn't in your Path environment variable. Before running SCons, make sure to add it by running SET Path=C:\mingw\bin;%Path% Obviously you need to replace C:\mingw\ with where you placed MinGW. Also are you passing BF_TOOLSET=mingw to SCons? You need to run "python.exe scons\scons.py BF_TOOLSET=mingw" from a 32-bit version of Python. Good luck, Caleb. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] trying to build with mingw32
On 25/04/2012 3:26 PM, Yousef Hurfoush wrote: > here is the patch i use: > cd Z:\Development\blender\blender-temp > set PATH=Z:\Development\compilers\Python26;%PATH% > set PATH=C:\MinGW\bin;C:\MinGW\lib;%PATH% > python scons\scons.py BF_TOOLSET=mingw > > and my mingw32 folder is the default c:\mingw > > anymore thoughts? > Ok, after running "set PATH=C:\MinGW\bin;C:\MinGW\lib;%PATH%", can you run "gcc -v" without any issues? Might be better to discuss this over IRC to avoid spam here :P ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] trying to build with mingw32
On 25/04/2012 3:46 PM, Yousef Hurfoush wrote: > there are no gcc in the bin folder which is strange! > but i have download the official mingw from their site with their installer > and i selected all the lib (checkboxs), and it downloaded the libs > and installed them, i don't know if there something went wrong! Strange, if you checked the "C Compiler" and "C++ Compiler" options when installing MinGW you should have what you need. Maybe it didn't download properly? ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
