Are openCV3.x binding planned anytime soon?

[spidergears]

No description provided.

[lazywei]

Sorry, given my current circumstance, I'm afraid that this won't be done in near future.
That being said, it's always welcome if you would like to send pull requests, or better yet, be a collaborator 👍

[RyanCopley]

@lazywei How is it going? I was wondering if you by chance have even a slice of time to even discuss this, what would we have to do to get this issue going forward? I can help with time and effort but I may need some guidance, do you have any time to discuss what you've learned so far and see if we can find a plan for what is needed to bind to the 3.x apis, then I could probably chip in some time to help.

I did some googling and I found these resources: http://zacg.github.io/blog/2013/06/06/calling-c-plus-plus-code-from-go-with-swig/

http://answers.opencv.org/question/54695/golang-binding-for-c-api/ (a post by you about this)

It seems as if you've already learned how to bind a C++ api (vs C). Does this mean that all that needs done is to define a module file which will tell the SWIG tool what code in the C++ project to expose in the resulting GO package. (link #1) ?

I'm eager to try to use opencv with go, but I want to be on the latest major version :-) I'll continue to look into this, but I would really appreciate if you could share what you've learned

[lazywei]

Hi @RyanCopley , thanks for your interest!

As for current progress, we have @chenziliang helping working on possible CV 3.x supports.

To support CV 3.x, we need to wrap C++ APIs, and this has been done in gocv subpackage. However, the wrapping is not yet complete. In fact, I only wrapped a little bit APIs for experiments. Current wrappers use SWIG for code generating. To add more wrappers, we need to find a better way to use SWIG.

If you would like to help, you may start with getting yourself familiar with SWIG and CV 3.x's C++ APIs (header files, for example). Any change should go to the gocv subpackage.

I agree we should shift our concentration to the major latest version. It would be awesome if we could have 3.x support.

Let me know if you have any questions or any thought on this.

Thanks!

[deadprogram]

Hi, @lazywei is there a branch where this work is being done yet? I also would like to help.

[lazywei]

@deadprogram thanks for your interest. Currently there is no branch for this. Please just make change to the master branch directly. All C++ binding should go to the gocv/ subdirectory.

Thanks.

[alisaifee]

👍 I would like to help as well. I wonder if we could start a gitter channel for this to discuss what needs to be done

[lazywei]

@alisaifee great idea. done, and invited you guys :-D

[codekoala]

How are things going on this front?

[RichLewis007]

Yes, are there any updates on progress in adding OpenCV 3?

[nordic-style]

You should mark #102 as duplicated.

And it seems that Matt started to work on this issue:
https://github.com/mlehner/go-opencv/commit/6e6733402a9e71b47c31929089f9892f005e13ec

[RichLewis007]

OK, thanks!

…

On Thu, Jun 22, 2017 at 8:53 PM, nordic-style ***@***.***> wrote: You should mark #102 <#102> as duplicated. And it seems that Matt started to work on this issue: ***@***.*** <mlehner/go-opencv@6e67334> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#60 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGJHUNYw8U0FQ34GreCXQyfPqGdzMe7ks5sGwyZgaJpZM4GVhl-> .

[deadprogram]

Please see my comment at #102 (comment)

Sorry to cross post, but seems relevant. Thank you!