UPBGE is a blender fork we do not maintain, so any questions
you have on UPBGE you'll have to sort out with the people who
work on it.
Their community page [1] has several options of contacting them.
Greetings,
Ray
[1] https://upbge.org/community.html
On 2020-04-10 12:58 a.m., Armani Bless vi
While i agree with "you should be able to build blender even with stock/system
libraries"
I however do not think that the bar for "oh we'll just add it to /extern"
should be as low as it appears to be. I'd be very much in favor of *NOT* adding
a behemoth like USD to `/extern` (~75 megs, twice t
I've always understood our position to be
- We do not plan to break or remove 32 bit support.
- Given we don't CI on 32 bit anymore, breakage can sometimes happen without us
knowing.
- If external parties supply patches to fix such breakage and they pass code
review, we merge them. Even if they
For the windows folks,
I have enabled clang-tidy for windows so you can now join in
on the fun, but there are some caveats that are important to
be aware of.
1- It will only be configured if WITH_CLANG_TIDY is on in cmake.
2- Only supported in the IDE, no ninja or command line support at
this
I can't say I'm super thrilled to build cairo on windows,
but if that's the direction we want to go, so be it.
--Ray
On 2020-12-09 11:19 a.m., Brecht Van Lommel via Bf-committers wrote:
> I'm not sure there exists a simple utility to convert SVG to PDF that we
> could include, if we want to go t
I'm unsure what this would achieve beyond making the lib update process more
frustrating than it already is?
The deps builder we have its singe purpose is to facilitate the building of our
SVN libs nothing more nothing less, its target audience is essentially 3 people
(the mac/linux/windows pla
Seems reasonable (and I agree) however playing devils advocate:
if we're going to need cairo down the road anyhow we may
as well rip that band-aid off now and deal with the pain
of building it rather than building libharu now and cairo later.
--Ray
On 2020-12-11 10:47 a.m., Brecht Van Lommel vi
--
> Ton Roosendaal - t...@blender.org - www.blender.org
> Chairman Blender Foundation, Director Blender Institute
> Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
>
>
> On 10/12/2020 16:02, Ray Molenkamp via Bf-committers wrote:
>> I'm unsure what this would a
orm perspective.
> I can gladly help out with the writing if no else from the "Platforms, Builds
> & Tests" module can pick that up.
I don't think the lack of documentation is due to lack of people wanting to
document it, but as you probably noticed by now getting a decision
Soo.. this thread has a good run, lots of good feedback, but it
still seems decision-less, I'll happily do the work to make this happen,
but who makes the final call here?
--Ray
On 2020-12-15 9:19 p.m., Campbell Barton via Bf-committers wrote:
> To follow up on previous messages:
>
> - On my
All,
What's going in with this file? there's 50+ commits in there
and I disagree with virtually every single hash I sampled
from it.
If we want to hide large changes made by automated tools like
the big clang-format [1] change, yeah awesome, but I really
would still like to see smaller and clearl
On 2020-12-28 12:47 p.m., Ankit wrote:
> Hello
> I'm getting used to it.
> I'll remove several commits soon, now that I have received the
> feedback on the last commit, and will use stricter conditions in the future.
I'd like to replace "stricter conditions" with "well defined/documented
conditio
in git blame.
>> If I see "cleanup" in the title, the onus is on the committer to make
>> sure that it really is a cleanup. If that promise is kept, I don't see
>> why a cleanup commit interests you.
>>
>>> Changes in this file don't even seem t
That seems somewhat strange and out of the blue (at least for me), the lack of
reasoning for putting them on hold especially for the Tuesday ones you seem
fond of is concerning, what am i missing here?
--Ray
On 2021-02-08 9:33 a.m., Dalai Felinto via Bf-committers wrote:
> Hi,
> The Monday (dev
i hear the Tuesday meetings are a joy
--Ray
On 2021-02-09 8:59 a.m., Dalai Felinto wrote:
> Hi Ray,
>
> Which reasons do you see to keep the meeting(s)?
>
> Thanks,
> Dalai
>
> Op ma 8 feb. 2021 om 17:46 schreef Ray Molenkamp via Bf-committers
> mailto:bf-committers@
uld be appreciated
--Ray
On 2021-02-09 9:14 a.m., Ray Molenkamp via Bf-committers wrote:
> i hear the Tuesday meetings are a joy
>
> --Ray
>
> On 2021-02-09 8:59 a.m., Dalai Felinto wrote:
>> Hi Ray,
>>
>> Which reasons do you see to keep the meeting(s)?
>>
>* 2.93 bcon2 on 17 February.
This is listed on developer.blender.org as march 17
on both the front page [1] and the 2.93 schedule [2]
Did this change, or is it a typo?
--Ray
[1] https://developer.blender.org/
[2] https://developer.blender.org/project/view/125/
On 2021-02-15 11:19 a.m., Dala
It felt somewhat strange to me for the modules
to present their targets 2 days before the bcon1
deadline, I mean at this point all work should
be done/in already, seems a little late to determine
their feasibility.
Perhaps it's better to do add a similar style
meeting earlier in the process to sol
All,
Normally I don't do notify bf-c on platform changes I do
but this one seemed note worthy.
I landed ASAN support (D7794) for windows a few
minutes ago, it requires the latest VS update (16.9)
but beyond that it functions the same way as it does
on Linux, just toggle `WITH_COMPILER_ASAN` ON i
All,
More and more code is getting converted to C++
and honestly couldn't be happier about that.
What I'm less thrilled about is the way this is
being done, devs work with GCC, don't test on
windows, violate the standard (use of designated
initializers in c++ breaks the build every...single
..tim
imho 3.9 is the only version they could have picked, the
proposed release date for 3.10 is 2021-10-04 [1]. While
the VFX platform aims to finalize in august [2]. I was
rather vocal last year for them putting versions on that
had not been released yet (some of which got delayed well
into 2021) I'm h
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 are much more verbose in their patch description,
some have visual aids (images/cli
May I suggest moving the change log to the bottom of
the page (or even better its own page) ?
While I absolutely love having the change log, having
users/devs scroll though it before they can learn
how to use the build infra structure seems less than
ideal, given the change log is not going to get
Dalai,
Think some small clarification is in order here
Jesse is a very capable and diverse developer [1]
Now he did have a few patches in my module (as he did
in many others), and while I will happily commit
contributors patches, there is a point where you go
"wait? why am I still committing patc
Is the developer wiki is the ideal place to
communicate with end-users?
There's no denying these are pretty good looking
docs with plenty of screenshots, the top of the
page is clearly aimed at developers and will
just scare off most end users that do manage to
find it. (end users are unlikely to
My official position is : The platform module is
not in the business of making library recommendations,
or deciding what library does or doesn't go into blender.
As long as the admins are willing to sign off on it,
we'll build any library you want, with whatever options
you require. When the rende
For people having ssl issues with arcanist, the easiest solution is
1) grab the latest cacert.pem from https://curl.se/docs/caextract.html
2) copy it to [arcanist_installation_folder]/resources/ssl/custom.pem
Pay attention to the slightly different filename it *NEEDS* to be
custom.pem the origina
All right, looks like we're tiptoeing around
the elephant in the room, time to rip that
Band-Aid off (feels like this metaphor kinda
got away from me, but I'm sticking with it!)
Let’s not beat around the bush, no-one has
ever complained about our OIIO, Boost, VDB or
TBB versions. People get ..pass
> I don't really feel great about Python
> being the only exception allowed to be digressed
> from the platform.
I think you're misunderstanding the VFX Platform goals,
it has nothing to do with asset compatibility throughout
the pipeline. Otherwise, it would specify what formats
would have to be
he same and it's reasonable to assume we
> continue being incompatible there. For other libraries, if it's not causing
> incompatibility I don't even see that as deviating from the VFX platform.
> If it does lead to incompatibility, I think we should take that into
> c
The reason that is, most of the people involved are in the
discussion are not in a position to make this decision
(and that includes me) We can have good arguments on either
side of following or not following, but none of us can
decide.
This is something that will have to be decided at the top.
It
While I do not mind the practical nuts and bolts of this
proposal at all, I do mind the language, referring to the
VFX Platform as something worth looking at regarding file
or platform compatibility is unfortunate.
The Platform as is makes no attempt to manage file compatibility
throughout the pip
of
> the build environment makes my life much easier. So, I throw what little say
> I have into getting Blender and the platform aligned.
>
> On Thu, Jan 20, 2022, 11:22 AM Ray Molenkamp via Bf-committers
> wrote:
>
> While I do not mind the practical nuts and bolts
All, After years of loyal service we will be retiring support for MSVC 2017,
making the new requirement at least MSVC 2019 16.9.16. The build scripts and
wiki will be updated in the coming days to remove VS2017 support. If you have
updated your VS 2019 installation in the last year you will like
All,
It's been years [1] (2018) since I last was rather
vocal on this subject, but how is this [2] still
happening? "Yes, blender deleted your data (and silently
at that), that means it's working correctly!" cannot
possibly be the best we can do, is it?
While I'm excited with all the directions b
ease to the other.
>
> -- Bastien
>
> On 5/9/22 21:12, Ray Molenkamp via Bf-committers wrote:
>> All,
>>
>> It's been years [1] (2018) since I last was rather
>> vocal on this subject, but how is this [2] still
>> happening? "Yes, blender deleted y
, and it was a pain
> in the butt.
>
> Could someone take a stab at explaining what this debate really is about,
> in such a way that both sides would feel fairly represented? All I know
> right now is that there's a disagreement about something that currently
> feels over my hea
The core team has bought blender to where it is today,
they seem to have a pretty good handle on things.
I'm not sure design by committee on bf-c is what
this problem was lacking.
Just give 'm time, guys, they got this.
--Ray
On 2022-05-17 6:19 p.m., Harley Acheson via Bf-committers wrote:
>> T
=8<==[Editors note]=8<==
I'll be honest I'm 100% convinced mailinator will ruin
the little formatting I have done, I put a copy of this
email on https://developer.blender.org/P3014.
=8<8<8<8<==
How much as I like the sentiment of "lets move to git will it
solve all these problems" lets
ing that
> Brecht asked for the SVN compression to be disabled due to some client
> problems. So, this will require some research, perhaps next week.
>
> Anyway, hopefully it helps a bit until I can review some more settings.
>
> Enjoy your weekend everyone!
>
>
> D
Except for you just now i don't think anyone is
questioning the need for version control on the
3rd party dependencies. This tree was there long
before i joined the blender project so can't give
any insights on any controversy in creating it.
However whenever this subject (why svn) comes up,
it te
I have to admit, I don't have a whole lot of experience with macs,
I have honestly no idea of the real-world impact of a version
bump. However, given we committed to follow the VFX platform for
2023/2024 which targets 11.0 for 2023 shouldn't we either :
a) Follow the VFX platform and Target 11.0
-
> Ton Roosendaal - t...@blender.org - www.blender.org
> Chairman Blender Foundation, CEO Blender Institute / Studio
> Buikslotermeerplein 161, 1025 ET Amsterdam, the Netherlands
>
>
> On 12/05/2022 22:17, Ray Molenkamp via Bf-committers wrote:
>> I don't think there&#x
All,
As some of you have possibly noticed, I have been making some
changes/cleanups to our build system, some new and foreign
concepts to some may have shown up.
I was planning to send an update about this once the work
was completed, but several community members have reached
with various levels
44 matches
Mail list logo
