You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've made a feature request to merge this codebase (or parts) with the official swig project: https://sourceforge.net/p/swig/feature-requests/94/
Not sure that this would lead to somewhere, but it would be great if other users would vote on that, because i would like this project to be kept alive.
Also donating to the apache foundation (maybe flex project) would be an option, if the original developers are not able to keep the project alive (no commits since 5(?) months, also no feedbacks for tickets)
The text was updated successfully, but these errors were encountered:
I don't think they're going to take it, as cross-bridge's branch of swig depends on using their own branch of llvm to parse the C/C++ headers. I don't know why they chose to do this, as swig contains its own parser, but it makes building crossbridge's swig extremely complicated.
Thanks for the insights, after reading trough more material regarding the topic I've realized that It's much more complicated than I've tought first. Anyway I'll give a shot with a fork.
Maybe some parts could be enhanced/changed to more modular, also I would like to see automated builds from the stable project. I'm not sure about the futures branch because it seems to me that those goals are too high to achieve any time soon (upgrading to new compiler versions / C++11 support).
I must say I'm pretty happy with the current capabilities of the stable branch (C and limited C++ support).
I've made a feature request to merge this codebase (or parts) with the official swig project:
https://sourceforge.net/p/swig/feature-requests/94/
Not sure that this would lead to somewhere, but it would be great if other users would vote on that, because i would like this project to be kept alive.
Also donating to the apache foundation (maybe flex project) would be an option, if the original developers are not able to keep the project alive (no commits since 5(?) months, also no feedbacks for tickets)
The text was updated successfully, but these errors were encountered: