Hi, so it is mostly a problem for Linux, not for Windows and Mac?
Regarding compilation we could build only audaspace in C++11 mode? We can also do 1 and 2, so you can then choose between 3 options (including old audaspace for Linux builds). I meant 2.78, not 2.48, sorry. Regards On 2015-04-15, 00:30 Sergey Sharybin wrote: > Hi, > > That'd be a good idea to cover benefits which can be measured by artists ;) > Are there gonna to be loads of bugfixes, new features? > > As for C++11 in general, there are several technical issues: > > - It'll piss off majority of the render farms and some studios which are > using Blender and which for one or another reason are using operation > systems like CentOS or even RHEL. We can't just ignore this fact when > making decision in here. > > - While majority of Blender is happy about C++11 it is still not fully > ready for this. For example you need latest versions of OIIO and OSL (which > are not released yet) in order to make compilation process smooth and > successful. > > - If you're using any C++11 subset which requires gcc-4.8 then you'll 100% > need to hold on such a change for until official Linux release environment > gets upgraded. Currently it uses gcc-4.7 and updating to newer gcc is real > PITA because it implies using newer libc, which also implies bumping > minimal system requirement for the official Linux builds. > > For packaging i wouldn't rely on it because not everyone is living on the > bleeding edge with RR Linux distros. To be honest, being accepted for Arch > does not convince me, i'll be more convinced once the library is accepted > into Debian (if it's be accepted into CentOS/RHEL i'll also be pretty much > convinced :). For until then sticking to an in-source lib is better idea. > > -------- > > Answering your request for comments: > > - If the library is more or less same size think 2) is better (less > intrusive at least) way to go. Additionally to that, you can also have > WITH_SYSTEM_AUDASPACE (same as we do with some other libraries). > - Not totally clear what exact version you meant instead 2.48, but there > are technical issues which needs to be addressed first. > > > On Wed, Apr 15, 2015 at 2:39 AM, Jörg Müller <[email protected]> wrote: > >> Hi all, >> >> the C++11 version of audaspace (Blender's audio library) [1] is ready to >> be used in Blender. The library is in a ready to release state and I >> have successfully built and used it on Windows, Mac and Linux. Idealy I >> would like to have it in the release of Blender 2.76. To integrate it >> back into the Blender source tree there are two possible solutions: >> >> 1. we have it as an dependency like most other libraries. This means >> that the prebuilt library is in the lib svn folder [2] for Windows and >> Mac. Linux developers would need to have it installed. There is a >> package [3] for Arch linux already for example, creating packages for >> other distributions shouldn't be too difficult. >> >> 2. we build it as part of our build system and put the source code in >> the extern folder like other libraries such as bullet or libmv. The >> current version is in the intern folder. >> >> I have a patch that implements solution 1 for Linux so far and it keeps >> the old version in intern and adds an option to cmake with which you can >> switch between old and new audaspace. >> >> To build the library a compiler with full C++11 compatibility is needed, >> that means clang starting with version 3.3 (lower might be enough for >> audaspace), gcc 4.8 and msvc 2013. Mingw doesn't work as they don't >> support std::thread yet for example. >> >> I am now asking for comments and suggestions and especially whether the >> first or second option are prefered. The plan would be to implement and >> test this then until 2.48 is released and merge it to master as soon as >> master is open after the 2.48 release. >> >> Regards, >> Jörg >> >> [1] https://github.com/neXyon/audaspace >> [2] https://svn.blender.org/svnroot/bf-blender/trunk/lib/ >> [3] https://aur.archlinux.org/packages/audaspace-git/ >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
