Mike D Pilsbury

I'm not sure that treating an empty string as a special case is the best approach. It may work for `gtk_frame_new`, but perhaps there are other situations were it wouldn't...

I've experimented with this a bit in the past. I found that when the code to be compiled was split across more files, it took longer to build. I suspect...

This isn't currently supported. Hopefully issue #20 will lay the groundwork allow to allow me to add some support for GList.

That's an interesting thought. I wasn't aware of the `--modversion` flag. However after a little bit of playing with a script, I'm not sure that it'll be easy to use...

And of course one may wish to build targetting earlier versions of libraries than those installed locally.

> your roll-your-own approach is going to break I am using pkg-config courtesy of the cgo comments in the `package.go` files. So I'm not sure what roll-your-own approach you're referring...

Strangely I can see those constants are defined in `glib-2.0/glib/gkeyfile.h`. I have glib `2.56.4`. However I cannot find any documentation for the constants. So I have blacklisted them from the...

What go build/run command are you running when this happens? Does the example in the readme work?

`lib/gobject/package.go` contains ```go // #cgo pkg-config: gobject-2.0 import "C" ``` Which should result in use of `pkg-config --libs gobject-2.0` by go build so that it includes the necessary linker flags...

I've got a handle on this now. A function (for example `g_converter_output_stream_new`) has no version information in the gir file. However it has a parameter with a type (in this...