Next hurdle on the "writing GTK libraries in Go" cleared: Devhelp2 files are now properly being created (meaning that LSPs and Manuals can pick them up), Blueprint is supported, libraries don't need to be initialized in order for GObject types to be registered and constructors are also no longer necessary to bind Go instances to the GObject instances!

Update: We have versioning, `pkg-config` support and better Go (&, in the future, Rust) bindings support! Tomorrow, let's see if we can tackle i18n support.

Show thread

Also properly read `g-ir-scanner` docs and figured out how the references to used libraries works in the `gi-docgen` tool. Soon, this shall all be done with Meson ofc, but still, it is nice to get the familiar with the actual CLI tools IMHO

Show thread

I will also say, it is very enticing to just use `go:embed` for resource files and skip the Meson step for those šŸ¤·ā€ā™€ļø If it weren't for gettext's inability to read from those then I'd probably go down that route

Show thread
Follow

@pojntfx can go:embed work even if the files to be embedded live in some other git repo, something that is not a go package but just whatever repo with files that you want to embed?

Ā· Web Ā· 0 Ā· 0 Ā· 0
Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml