-
|
While I'm currently reading through the manual, I'm eager to know whether this capability is actually "ready to use" in SWIG, how "experimental" it still is, and how to run it. Typical runs look like The SWIG homepage lists in the 4.3.0 summary "Add experimental support for C as a target language" as the top point. The Wiki here and StackOverflow / web-search results OTOH refer to many-years-ago GSoC explorations that are probably no longer pertinent or operational. So what's "the actual state of affairs, right now" on this? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
And now I found extensive doc page https://www.swig.org/Doc4.3/C.html — will probably mark & close this thread shortly, after I have read through it. =) |
Beta Was this translation helpful? Give feedback.
-
|
SWIG is quite versatile, and the exact command depends on the language module you're using. For C or C++ integration, the typical workflow would involve specifying the target language, such as swig -python example.i or swig -tcl example.i. If you're exploring a newer or less common feature, checking the SWIG documentation or release notes for specific instructions is a good step. It's always a good idea to experiment with simple examples first and verify functionality before using it in larger projects. |
Beta Was this translation helpful? Give feedback.
And now I found extensive doc page https://www.swig.org/Doc4.3/C.html — will probably mark & close this thread shortly, after I have read through it. =)