Recently new precompiled libraries have been committed to SVN.
Anyone using Linux pre-compiled libraries should check out
"linux_x86_64_glibc_228" which replaces the old "linux_centos7_x86_64"
libraries.
While master builds with both old and new libraries for the moment,
we'll eventually remove the
Hi, a recent update I made to Linux libraries removed then added new
libraries (instead of adding/removing individual files),
it seems to have caused problems updating with unversioned files in
these directories (Python's "__pycache__/" in particular).
I'm not sure how many users this impacted, bu
On Sun, Jan 23, 2022 at 12:22 AM Brian Savery via Bf-committers
wrote:
>
> > At some point strategic decisions like this should have tangible
> > benefits beyond the *possability* of attracting a user base. Maybe it
> > will be different this time - in that case there should be an
> > explanation
On Sat, Jan 22, 2022 at 12:28 AM Dalai Felinto via Bf-committers
wrote:
>
> Hi,
> I believe Blender should stick to the VFX platform.
>
> After all that has been said, I think it may boil down to making a decision
> between immediate known benefits and strategic uncertain long-term benefits.
>
> *
This discussion seems to suffer the same fate as other VFX platform
threads... fizzle out with no conclusion.
Could we at least confirm the current status - that is: Python can be
upgraded without being limited by the VFX platform. If someone
proposes to change this - it's fine.
As it happens Se
On Mon, Jan 17, 2022 at 11:12 PM Bastien Montagne via Bf-committers
wrote:
>
> Hi Sergey and all, and thanks for this proposition.
>
> This proposal makes complete sense to me. I do not see any benefit for
> Blender to stick to a strict compatibility with VFX platform, but indeed
> ensuring a file
On Mon, Jan 17, 2022 at 9:24 PM Sergey Sharybin via Bf-committers
> I agree that the outcome should be much more prominently communicated.
> That's what I think should happen as an outcome of discussion in this
> thread: we come up with policy and explicitly communicate it.
+1, just noting that t
As far as I'm aware, the decision for Blender *not* to follow the VFX
platform for Python is still in place (allowing us to follow Python's
release schedule, unless there are good reasons not to).
Last time the topic came up was May 2021, the discussion petered out
and there were no conclusions fr
Hi, the fast method wasn't based on existing papers.
It works using triangle-triangle intersection between two BVH trees,
those intersections are used to perform cut the geometry with
additional functionality to handle holes in faces.
Ray-casting is then used to determine what is inside/outside.
O
On Tue, Nov 16, 2021 at 9:03 PM Sybren A. Stüvel via Bf-committers
wrote:
>
> Hi all,
>
> Recently there has been a discussion about the location of code
> documentation (as in, the in-source documentation comments). The gist of it
> is that, in my opinion, documentation of the public interface of
Hi, the code-style docs [0] were recently updated based on T81452 [1]
This mainly formalizes what's already done in a majority of the code,
if you're actively developing & committing code it's worth checking.
[0]: https://wiki.blender.org/wiki/Style_Guide/C_Cpp#Comments
[1]: https://developer.ble
On Fri, Jun 4, 2021 at 7:51 PM Sybren A. Stüvel via Bf-committers
wrote:
>
> On Wed, 2 Jun 2021 at 07:56, Campbell Barton via Bf-committers <
> bf-committers@blender.org> wrote:
>
> > If the proposed policies are followed to the letter, we end up in
> > situations
On Wed, Jun 2, 2021 at 6:20 PM Sergey Sharybin via Bf-committers
wrote:
>
> Campbell, those are valid points, but here is what I propose:
>
> (a) Focus on making already-agreed-on topics public, go into more
> specific cases later.
Sergey, sounds good.
Since these rules are on our official wiki I
On Wed, Jun 2, 2021 at 5:22 PM Ray Molenkamp via Bf-committers
wrote:
>
> I'm somewhat confused on the goal some of the (proposed?) rules.
> But I'll just pick on the "Patch description should match the
> commit message."-rule for now not to make this longer than it
> needs to be.
>
> Most people
Hi, there are a few cases this document doesn't cover
(understandably as they're not so typical).
How to best make updates to a patch?
While proposing changes and having the patch author apply them is
almost always preferred, there are times when it is less t
I'm not too keen on tying ourselves to the VFX platform again (for
Python versions at least).
The VFX platform has a track record of not upgrading Python for
reasons that don't make sense for Blender (availability of Python-QT
bindings & some companies simply not wanting to upgrade).
Now Blender
To follow up on previous messages:
- On my system the stripped library is ~830kb,
over half of the libraries file-size is binary data for fonts and
character encoding tables,
if we wanted we could remove these - bringing the size down to ~350kb.
- This library is available on mainstream Linux
; development time to make sure the existing solution is robust enough to
> be replaced if needs be.
>
> Regards,
> Dalai
>
> On 09-12-2020 23:34, Campbell Barton via Bf-committers wrote:
>> rsvg-convert (which uses cairo), is a utility that converts SVG to
>> PDF, it c
rsvg-convert (which uses cairo), is a utility that converts SVG to
PDF, it can create multi-page PDF's from many SVG's too.
If for some reason we need more control then a command line utility
provides, there are Python multiple options regarding bindings for
cairo & svg conversion.
From what I can
Hi Antonion,
From what I can tell libharu hasn't been very active since 2013, their
site states they're looking for a new maintainer.
Would we become the defacto maintainers of this library?
I checked their issue tracker, while many reports are support requests
and build issues, there are some mo
Hi, this proposal intends to make formal some existing conventions for
Blender's code-comments,
as well as a few minor changes to improve our comments.
https://developer.blender.org/T81452
--
- Campbell
___
Bf-committers mailing list
Bf-committers@blen
21 matches
Mail list logo
