diff options
| author | Felix Schwitzer <flx107809@gmail.com> | 2018-06-11 18:24:41 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2018-06-12 13:55:53 (GMT) |
| commit | 156138d5f1d15a79f86db64bbe2dd6043fd3b43f (patch) | |
| tree | cf9f709e6574c9f1022f5af29a9cea3458f91930 /Source/cmCustomCommandGenerator.h | |
| parent | 90ebc32d9e7400a590973b30c99f2986bcb2b755 (diff) | |
| download | CMake-156138d5f1d15a79f86db64bbe2dd6043fd3b43f.zip CMake-156138d5f1d15a79f86db64bbe2dd6043fd3b43f.tar.gz CMake-156138d5f1d15a79f86db64bbe2dd6043fd3b43f.tar.bz2 | |
UseSWIG: Fix handling of `SWIG_MODULE_NAME` source file property
Fix a typo from commit 0bef9eb410 (UseSWIG: modernize module,
2018-01-29) that caused `UseSWIG` to ignore an eventually set property
`SWIG_MODLUE_NAME`.
Building multiple python modules using the mentioned property as
described in the docs could lead to an invalid, or even worse,
inconsistent `build.ninja` file. The reason is that the generated list
of support files was not unique. For each module the support file was
always named the same, namely `path/to/builddir/MODULENAME.py`.
Diffstat (limited to 'Source/cmCustomCommandGenerator.h')
0 files changed, 0 insertions, 0 deletions