d973355b3a
Using ClangBuildAnalyzer on the whole Blender build, it was pointing out that BLI_math.h is the heaviest "header hub" (i.e. non tiny file that is included a lot). However, there's very little (actually zero) source files in Blender that need "all the math" (base, colors, vectors, matrices, quaternions, intersection, interpolation, statistics, solvers and time). A common use case is source files needing just vectors, or just vectors & matrices, or just colors etc. Actually, 181 files were including the whole math thing without needing it at all. This change removes BLI_math.h completely, and instead in all the places that need it, includes BLI_math_vector.h or BLI_math_color.h and so on. Change from that: - BLI_math_color.h was included 1399 times -> now 408 (took 114.0sec to parse -> now 36.3sec) - BLI_simd.h 1403 -> 418 (109.7sec -> 34.9sec). Full rebuild of Blender (Apple M1, Xcode, RelWithDebInfo) is not affected much (342sec -> 334sec). Most of benefit would be when someone's changing BLI_simd.h or BLI_math_color.h or similar files, that now there's 3x fewer files result in a recompile. Pull Request #110944
112 lines
2.7 KiB
C++
112 lines
2.7 KiB
C++
/* SPDX-FileCopyrightText: 2023 Blender Foundation
|
|
*
|
|
* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
|
|
/** \file
|
|
* \ingroup pymathutils
|
|
*/
|
|
|
|
#include <Python.h>
|
|
|
|
#include "mathutils.h"
|
|
#include "mathutils_interpolate.h"
|
|
|
|
#include "BLI_math_geom.h"
|
|
#include "BLI_utildefines.h"
|
|
|
|
#ifndef MATH_STANDALONE /* define when building outside blender */
|
|
# include "MEM_guardedalloc.h"
|
|
#endif
|
|
|
|
/*-------------------------DOC STRINGS ---------------------------*/
|
|
PyDoc_STRVAR(M_Interpolate_doc, "The Blender interpolate module");
|
|
|
|
/* ---------------------------------WEIGHT CALCULATION ----------------------- */
|
|
|
|
#ifndef MATH_STANDALONE
|
|
|
|
PyDoc_STRVAR(M_Interpolate_poly_3d_calc_doc,
|
|
".. function:: poly_3d_calc(veclist, pt)\n"
|
|
"\n"
|
|
" Calculate barycentric weights for a point on a polygon.\n"
|
|
"\n"
|
|
" :arg veclist: list of vectors\n"
|
|
" :arg pt: point"
|
|
" :rtype: list of per-vector weights\n");
|
|
static PyObject *M_Interpolate_poly_3d_calc(PyObject * /*self*/, PyObject *args)
|
|
{
|
|
float fp[3];
|
|
float(*vecs)[3];
|
|
Py_ssize_t len;
|
|
|
|
PyObject *point, *veclist, *ret;
|
|
int i;
|
|
|
|
if (!PyArg_ParseTuple(args, "OO:poly_3d_calc", &veclist, &point)) {
|
|
return nullptr;
|
|
}
|
|
|
|
if (mathutils_array_parse(
|
|
fp, 2, 3 | MU_ARRAY_ZERO, point, "pt must be a 2-3 dimensional vector") == -1)
|
|
{
|
|
return nullptr;
|
|
}
|
|
|
|
len = mathutils_array_parse_alloc_v(((float **)&vecs), 3, veclist, __func__);
|
|
if (len == -1) {
|
|
return nullptr;
|
|
}
|
|
|
|
if (len) {
|
|
float *weights = static_cast<float *>(MEM_mallocN(sizeof(float) * len, __func__));
|
|
|
|
interp_weights_poly_v3(weights, vecs, len, fp);
|
|
|
|
ret = PyList_New(len);
|
|
for (i = 0; i < len; i++) {
|
|
PyList_SET_ITEM(ret, i, PyFloat_FromDouble(weights[i]));
|
|
}
|
|
|
|
MEM_freeN(weights);
|
|
|
|
PyMem_Free(vecs);
|
|
}
|
|
else {
|
|
ret = PyList_New(0);
|
|
}
|
|
|
|
return ret;
|
|
}
|
|
|
|
#endif /* MATH_STANDALONE */
|
|
|
|
static PyMethodDef M_Interpolate_methods[] = {
|
|
#ifndef MATH_STANDALONE
|
|
{"poly_3d_calc",
|
|
(PyCFunction)M_Interpolate_poly_3d_calc,
|
|
METH_VARARGS,
|
|
M_Interpolate_poly_3d_calc_doc},
|
|
#endif
|
|
{nullptr, nullptr, 0, nullptr},
|
|
};
|
|
|
|
static PyModuleDef M_Interpolate_module_def = {
|
|
/*m_base*/ PyModuleDef_HEAD_INIT,
|
|
/*m_name*/ "mathutils.interpolate",
|
|
/*m_doc*/ M_Interpolate_doc,
|
|
/*m_size*/ 0,
|
|
/*m_methods*/ M_Interpolate_methods,
|
|
/*m_slots*/ nullptr,
|
|
/*m_traverse*/ nullptr,
|
|
/*m_clear*/ nullptr,
|
|
/*m_free*/ nullptr,
|
|
};
|
|
|
|
/*----------------------------MODULE INIT-------------------------*/
|
|
|
|
PyMODINIT_FUNC PyInit_mathutils_interpolate()
|
|
{
|
|
PyObject *submodule = PyModule_Create(&M_Interpolate_module_def);
|
|
return submodule;
|
|
}
|