Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-06-22Cleanup: compiler warningBrecht Van Lommel
2020-06-22Python: support building again version 3.9 (unreleased)Campbell Barton
Resolves T78089, no functional changes.
2020-06-17Cleanup: clang-formatBrecht Van Lommel
2020-06-15API docs: mathutils leaked markupTobias Heinke
Reviewed By: Blendify Differential Revision: https://developer.blender.org/D8021
2020-05-11Merge branch 'blender-v2.83-release'Philipp Oeser
2020-05-11Fix mathutils box_pack_2d docstringPhilipp Oeser
Differential Revision: https://developer.blender.org/D7667
2020-05-04Fix T76399: Wrong API docs for mathutils.Vector.dotJacques Lucke
2020-03-19Cleanup: `make format` after SortedIncludes changeDalai Felinto
2020-03-09Cleanup: Replace ABS/SQUARE/CUBE with function callsSergey Sharybin
While it might be handy to have type-less functionality which is similar to how C++ math is implemented it can not be easily achieved with just preprocessor in a way which does not have side-effects on wrong usage. There macros where often used on a non-trivial expression, and there was at least one usage where it was causing an actual side effect/bug on Windows (see change around square_f(sh[index++]) in studiolight.c). For such cases it is handy to have a function which is guaranteed to have zero side-effects. The motivation behind actually removing the macros is that there is already a way to do similar calculation. Also, not having such macros is a way to guarantee that its usage is not changed in a way which have side-effects and that it's not used as an inspiration for cases where it should not be used. Differential Revision: https://developer.blender.org/D7051
2020-03-04Cleanup: replace CLAMP macros with functionsCampbell Barton
2020-02-29Made BLI_delaunay_2d_cdt_calc better at tiny feature elimination.Howard Trickey
The 'random' unit tests and some examples from the new boolean code triggered asserts and crashes. This fixes those. There is a new flag in the input that optionally disables a pass over input to snap segment edges to other segments.
2020-02-20Fix ushort compiler errors in WindowsAntonio Vazquez
ushort is not supported
2020-02-20Cleanup: use named unsigned types in the Python APICampbell Barton
2020-02-20mathutils: support for to_2x2 as well as non-square matricesCampbell Barton
2020-02-20mathutils: support Vector.rotate for 2D vectorsTiago Chaves
2020-02-10Cleanup/refactor: Rename `BKE_library` files to `BKE_lib`.Bastien Montagne
Note that `BKE_library.h`/`library.c` were renamed to `BKE_lib_id.h`/`lib_id.c` to avoid having a too generic name here. Part of T72604.
2020-01-27Document that tessellate_polygon() doesn't handle degenerate geometrySybren A. Stüvel
This 'fixes' T68554: 'API mathutils.geometry.tessellate_polygon returns bad results sometimes' by documenting the limitations of the current implementation. I've also added a unit test for the function, so that any change in this behaviour will get noticed. No functional changes.
2020-01-23CMake: Refactor external dependencies handlingSergey Sharybin
This is a more correct fix to the issue Brecht was fixing in D6600. While the fix in that patch worked fine for linking it broke ASAN runtime under some circumstances. For example, `make full debug developer` would compile, but trying to start blender will cause assert failure in ASAN (related on check that ASAN is not running already). Top-level idea: leave it to CMake to keep track of dependency graph. The root of the issue comes to the fact that target like "blender" is configured to use a lot of static libraries coming from Blender sources and to use external static libraries. There is nothing which ensures order between blender's and external libraries. Only order of blender libraries is guaranteed. It was possible that due to a cycle or other circumstances some of blender libraries would have been passed to linker after libraries it uses, causing linker errors. For example, this order will likely fail: libbf_blenfont.a libfreetype6.a libbf_blenfont.a This change makes it so blender libraries are explicitly provided their dependencies to an external libraries, which allows CMake to ensure they are always linked against them. General rule here: if bf_foo depends on an external library it is to be provided to LIBS for bf_foo. For example, if bf_blenkernel depends on opensubdiv then LIBS in blenkernel's CMakeLists.txt is to include OPENSUBDIB_LIBRARIES. The change is made based on searching for used include folders such as OPENSUBDIV_INCLUDE_DIRS and adding corresponding libraries to LIBS ion that CMakeLists.txt. Transitive dependencies are not simplified by this approach, but I am not aware of any downside of this: CMake should be smart enough to simplify them on its side. And even if not, this shouldn't affect linking time. Benefit of not relying on transitive dependencies is that build system is more robust towards future changes. For example, if bf_intern_opensubiv is no longer depends on OPENSUBDIV_LIBRARIES and all such code is moved to bf_blenkernel this will not break linking. The not-so-trivial part is change to blender_add_lib (and its version in Cycles). The complexity is caused by libraries being provided as a single list argument which doesn't allow to use different release and debug libraries on Windows. The idea is: - Have every library prefixed as "optimized" or "debug" if separation is needed (non-prefixed libraries will be considered "generic"). - Loop through libraries passed to function and do simple parsing which will look for "optimized" and "debug" words and specify following library to corresponding category. This isn't something particularly great. Alternative would be to use target_link_libraries() directly, which sounds like more code but which is more explicit and allows to have more flexibility and control comparing to wrapper approach. Tested the following configurations on Linux, macOS and Windows: - make full debug developer - make full release developer - make lite debug developer - make lite release developer NOTE: Linux libraries needs to be compiled with D6641 applied, otherwise, depending on configuration, it's possible to run into duplicated zlib symbols error. Differential Revision: https://developer.blender.org/D6642
2019-12-20Cleanup: remove redundant 'char *' castsCampbell Barton
2019-11-26PyAPI: add Quaternion.make_compatibleCampbell Barton
2019-11-15Merge branch 'blender-v2.81-release'Campbell Barton
2019-11-15Docs: correct indent for to_swing_twist docstringCampbell Barton
2019-11-06Mathutils: expose the utility to find the closest point of a triangle.Alexander Gavrilov
This computation is complex and useful enough to expose the existing C math utility used by BVH nearest to Python. Otherwise this requires the use of intersect_point_tri and multiple intersect_point_line calls with some added vector math. Differential Revision: https://developer.blender.org/D6200
2019-10-17Cleanup: spellingCampbell Barton
Also remove historic bftgl reference.
2019-10-16Cleanup: warnings building with Python 3.8Campbell Barton
2019-10-09PyAPI: drop Vector requirement for tessellate_polygonCampbell Barton
Use mathutils_array_parse which converts any sequence of numbers.
2019-10-09PyAPI: avoid normal calculation for tessellate_polygonCampbell Barton
Use fixed normal for 2D input, no need to calculate it.
2019-09-30Cleanup: spellingCampbell Barton
2019-09-23Fix T70177: Crash when calling to_track_quat() without argumentsJacques Lucke
2019-09-22Mathutils: expose the swing + twist Quaternion decomposition to Python.Alexander Gavrilov
This decomposition is useful in rigging, and involves a math trick.
2019-09-07Cleanup: use post increment/decrementCampbell Barton
When the result isn't used, prefer post increment/decrement (already used nearly everywhere in Blender).
2019-08-17Cleanup: spellingCampbell Barton
2019-08-16Cleanup: spellingCampbell Barton
2019-08-14Cleanup: move trailing comments to avoid wrapping codeCampbell Barton
Some statements were split across multiple lines because of their trailing comments. In most cases it's clearer to put the comments above.
2019-08-13Add mathutils.geometry.delaunay_2d_cdt() function to Python API.Howard Trickey
Provides Python API access to recently added Constrained Delaunay Triangulation routine. Reviewed in D5467.
2019-08-11BLI_math: add isect_tri_tri_v2, wrap via mathutils.geometryCampbell Barton
2019-08-04Cleanup: spellingCampbell Barton
2019-08-01Cleanup: use _ex suffix instead of _extCampbell Barton
Convention is to use ex, not ext for extended versions of a functions.
2019-07-10Cleanup: avoid line breaks from trailing commentsCampbell Barton
2019-07-04Cleanup: remove redundant castCampbell Barton
2019-06-12Cleanup: spelling in commentsCampbell Barton
2019-05-19Python API: add a Matrix.Diagonal constructor to mathutils.Alexander Gavrilov
For some reason there seems to be no way to do the very simple and obvious task of converting a scale vector to a matrix via mathutils. The Matrix.Scale constructor does something complicated instead. Reviewers: brecht, campbellbarton Differential Revision: https://developer.blender.org/D4893
2019-05-03Revert "Cleanup: add semicolon after PyObject_VAR_HEAD"Campbell Barton
This reverts commit a01bcfa6366f893fbc8fdbf537d91ece4832ea03. This causes MSVC2019 build to fail with error C2059 Unfortunately this means we have to put up with bad formatting in Python structs.
2019-05-03Cleanup: add semicolon after PyObject_VAR_HEADCampbell Barton
clang-format doesn't expand macros, add semicolon to prevent misleading formatting.
2019-04-29Cleanup: comments (long lines) in pythonCampbell Barton
2019-04-24Cleanup: sort CMake include pathsCampbell Barton
2019-04-20Cleanup: quiet extra-semicolon warningCampbell Barton
2019-04-18Cleanup: comment blocksCampbell Barton
2019-04-17Fix T63673: Wrong api documentation for Quaternion.dot(other)Jacques Lucke
2019-04-17ClangFormat: apply to source, most of internCampbell Barton
Apply clang format as proposed in T53211. For details on usage and instructions for migrating branches without conflicts, see: https://wiki.blender.org/wiki/Tools/ClangFormat