Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: using with recent SWIG and Go #73

Open
mar1ged opened this issue Jan 16, 2020 · 2 comments
Open

Question: using with recent SWIG and Go #73

mar1ged opened this issue Jan 16, 2020 · 2 comments

Comments

@mar1ged
Copy link

mar1ged commented Jan 16, 2020

From an outside standpoint I have the impression that some of the tricks you had to use might be absolete when using wxgo/wxwidgets in combination with SWIG 4.x and Go 1.3

Can you share your expertise in this ?

@dontpanic92
Copy link
Owner

dontpanic92 commented Jan 19, 2020

I didn't take a close track to the recent versions of SWIG and Go. Just now I took a look the release notes on SWIG and Go but it looks like few changes are related to the tricks we did for wxGo.

Basically our private fork of SWIG are focused on reducing the wrapper size and provide possible easier lifetime management, together with some other minor changes. It looks like the development of the Go backend in SWIG is in a very slow cadence and still missing this two features that we want.

Another trick for Golang is the workaround of "Invalid flag". This can be eliminate for the latest golang I believe

@mar1ged
Copy link
Author

mar1ged commented Jan 20, 2020

Thanks for sharing your insights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants