You can add as a benefit to your module that it avoids the *supply chain nightmare* that thereceipe/qt is (as you describe the latter: "It works by making IPC calls to a separate C++ binary downloaded at runtime from a site under the maintainer's control. This may be less performant than calling Qt directly.")
On Thursday, September 26, 2024 at 5:36:51 AM UTC+2 mappu wrote: > Hi everyone, I've recently been working on a new Qt Widgets binding for Go. > > You can check it out here: https://github.com/mappu/miqt > > Qt is a popular LGPL C++ framework that is mostly famous for Qt Widgets, > a traditional desktop GUI toolkit, crossplatform for Windows, macOS, > Linux, and mobile. There have been many Qt bindings for Go in the past, > the most well known is https://github.com/therecipe/qt . However, > therecipe's bindings were LGPL. LGPL is somewhat uncommon for Go > packages because Go is oriented for static linking, so it was extremely > difficult to legally use therecipe's bindings without incurring GPL > virality. The primary benefit of "miqt" is the bindings themselves are > MIT-licensed, allowing for Go's normal static linking to work well. Of > course you must still abide by Qt's own LGPL license. > > Miqt is still young but is compiling and working well on most platforms > already. If you were using therecipe/qt or any other Qt binding for Go > i'd appreciate if you could try miqt and raise issues if you experience > any problems, > > Thanks for your attention, > mappu > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7f44195f-45b5-4f6f-96b8-41f9cf828aa2n%40googlegroups.com.
