/usr/include/vtk-6.3/vtkPython.h is in libvtk6-dev 6.3.0+dfsg1-11build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 | /*=========================================================================
Program: Visualization Toolkit
Module: vtkPython.h
Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
All rights reserved.
See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
This software is distributed WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the above copyright notice for more information.
=========================================================================*/
#ifndef vtkPython_h
#define vtkPython_h
#include "vtkPythonConfigure.h"
#include "vtkABI.h"
/*
Use the real python debugging library if it is provided.
Otherwise use the "documented" trick involving checking for _DEBUG
and undefined that symbol while we include Python headers.
Update: this method does not fool Microsoft Visual C++ 8 anymore; two
of its header files (crtdefs.h and use_ansi.h) check if _DEBUG was set
or not, and set flags accordingly (_CRT_MANIFEST_RETAIL,
_CRT_MANIFEST_DEBUG, _CRT_MANIFEST_INCONSISTENT). The next time the
check is performed in the same compilation unit, and the flags are found,
and error is triggered. Let's prevent that by setting _CRT_NOFORCE_MANIFEST.
*/
#if defined(_DEBUG) && !defined(VTK_WINDOWS_PYTHON_DEBUGGABLE)
# define VTK_PYTHON_UNDEF_DEBUG
// Include these low level headers before undefing _DEBUG. Otherwise when doing
// a debug build against a release build of python the compiler will end up
// including these low level headers without DEBUG enabled, causing it to try
// and link release versions of this low level C api.
# include <basetsd.h>
# include <assert.h>
# include <ctype.h>
# include <errno.h>
# include <io.h>
# include <math.h>
# include <stdarg.h>
# include <stddef.h>
# include <stdio.h>
# include <stdlib.h>
# include <string.h>
# include <sys/stat.h>
# include <time.h>
# include <wchar.h>
# undef _DEBUG
# if defined(_MSC_VER)
# define _CRT_NOFORCE_MANIFEST 1
# endif
#endif
/* We used to try to #undef feature macros that Python.h defines
to avoid re-definition warnings. However, such warnings usually
indicate a violation of Python's documented inclusion policy:
"Since Python may define some pre-processor definitions which
affect the standard headers on some systems, you must include
Python.h before any standard headers are included."
(http://docs.python.org/c-api/intro.html#include-files)
To avoid re-definitions warnings, ensure "vtkPython.h" is included
before _any_ headers that define feature macros, whether or not
they are system headers. Do NOT add any #undef lines here. */
#if defined(_MSC_VER)
# pragma warning (push, 1)
#endif
#if defined(_MSC_VER) && _MSC_VER >= 1800
#define HAVE_ROUND
#endif
#include <Python.h>
#if defined(_MSC_VER) && _MSC_VER >= 1800
#undef HAVE_ROUND
#endif
#if defined(_MSC_VER)
# pragma warning (pop)
#endif
#ifdef VTK_PYTHON_UNDEF_DEBUG
# define _DEBUG
# undef VTK_PYTHON_UNDEF_DEBUG
#endif
#if (PY_VERSION_HEX & 0xFFFF0000) != (VTK_PYTHON_VERSION_HEX & 0xFFFF0000)
#error "Python.h is different version from what VTK was configured with!!"
#endif
#endif
|