4ac3c87a29
Ensure that SWIG_VERSION is defined both at SWIG-time and in the generated C/C++ wrapper code (it was only defined in the wrapper for some target languages previously). SWIGGO and SWIGJAVASCRIPT are now defined in the generated wrappers to match behaviour for all other target languages. Stop defining SWIGVERSION in the wrapper. This only happened as a side-effect of how SWIG_VERSION was defined but was never documented and is redundant. The new testcase also checks that SWIG is defined at SWIG-time but not in the generated wrapper, and that exactly one of a list of target-language specific macros is defined. Fixes #1050
17 lines
695 B
Text
17 lines
695 B
Text
/* -----------------------------------------------------------------------------
|
|
* Define SWIG_VERSION
|
|
* ----------------------------------------------------------------------------- */
|
|
|
|
/* Define SWIG_VERSION in the interface and the wrapper code.
|
|
*
|
|
* Best practice is to use SWIG-time checks for SWIG_VERSION, but SWIG_VERSION
|
|
* was unintentionally defined like this for many years, and while it was never
|
|
* documented there are likely user interface files which rely on it.
|
|
*/
|
|
%define %define_swig_version_()%#define SWIG_VERSION_ SWIG_VERSION %enddef
|
|
%insert("header") {
|
|
%define_swig_version_()
|
|
%#define SWIG_VERSION SWIG_VERSION_
|
|
%#undef SWIG_VERSION_
|
|
}
|
|
#undef %define_swig_version_
|