When using clangd or running clang-tidy on headers there are currently many errors. These are noisy in IDEs, make auto fixes impossible, and break features like code completion, refactoring and navigation. This makes source/blender headers work by themselves, which is generally the goal anyway. But #includes and forward declarations were often incomplete. * Add #includes and forward declarations * Add IWYU pragma: export in a few places * Remove some unused #includes (but there are many more) * Tweak ShaderCreateInfo macros to work better with clangd Some types of headers still have errors, these could be fixed or worked around with more investigation. Mostly preprocessor template headers like NOD_static_types.h. Note that that disabling WITH_UNITY_BUILD is required for clangd to work properly, otherwise compile_commands.json does not contain the information for the relevant source files. For more details see the developer docs: https://developer.blender.org/docs/handbook/tooling/clangd/ Pull Request: https://projects.blender.org/blender/blender/pulls/132608
33 lines
983 B
C++
33 lines
983 B
C++
/* SPDX-FileCopyrightText: 2023 Blender Authors
|
|
*
|
|
* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
|
|
/** \file
|
|
* \ingroup pythonintern
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <Python.h>
|
|
|
|
#include <stdbool.h>
|
|
|
|
/**
|
|
* For faster execution we keep a special dictionary for py-drivers, with
|
|
* the needed modules and aliases.
|
|
*/
|
|
int bpy_pydriver_create_dict();
|
|
/**
|
|
* For PyDrivers
|
|
* (drivers using one-line Python expressions to express relationships between targets).
|
|
*/
|
|
extern PyObject *bpy_pydriver_Dict;
|
|
|
|
extern bool BPY_driver_secure_bytecode_test_ex(PyObject *expr_code,
|
|
PyObject *py_namespace_array[],
|
|
const bool verbose,
|
|
const char *error_prefix);
|
|
extern bool BPY_driver_secure_bytecode_test(PyObject *expr_code,
|
|
PyObject *py_namespace,
|
|
const bool verbose);
|