en un clic
swig-test
// Run SWIG test suite for specific languages. Use when testing SWIG changes, verifying language support, debugging test failures, or running regression tests.
// Run SWIG test suite for specific languages. Use when testing SWIG changes, verifying language support, debugging test failures, or running regression tests.
| name | swig-test |
| description | Run SWIG test suite for specific languages. Use when testing SWIG changes, verifying language support, debugging test failures, or running regression tests. |
| argument-hint | Specify language (e.g., python, java) and optionally a single test name |
make in the root directory.make check-[language]-test-suite (e.g., make check-python-test-suite).make -j[n] check-[language]-test-suite to speed up on multi core systems that have n cores.cd Examples/test-suite/[language]/make -s [testcase].cpptest (for C++), make -s [testcase].ctest (for C), or make -s [testcase].multicpptest (for multi module).make -s ret_by_value.cpptest-s flag.make -s [testcase].cleanAuthor and edit chapters of the SWIG Users Manual under Doc/Manual: chapter conventions, manual heading anchors, the four content `<div>` styles (code / targetlang / shell / diagram), the auto generated section TOC, the `make` targets that renumber headings and validate HTML, and the rules for cross document anchored links.
Debug the SWIG compiler itself: -debug-* command line flags, parse tree dumps (text and XML), gdb with the swigprint/locswigprint helpers from Tools/swig.gdb, valgrind via the SWIGTOOL/RUNTOOL test suite hooks, and DOH_DEBUG_MEMORY_POOLS for memory corruption diagnosis.