I used to build Glib and various Gtk2/Gtk3 modules on Windows 7 - and provide binaries of those builds.
From memory, the key to success was to have a working pkg-config.exe in the PATH. (I used MSYS2's pkg-config.exe, but Cygwin's might also be ok.)
With a functional pkg-config.exe in the path, and a correctly set PKG_CONFIG_PATH environment variable, installing Glib was as simple as obtaining and extracting the Glib source, cd'ing to the top-level source directory and running:
perl Makefile.PL
gmake test
gmake install
If you go that trouble and it still doesn't work, please post again, and I'll provide the necessary amendments (which I'm sure will come to mind once I see the error messages).
If you want to persist without a functioning pkg-config.exe (which I don't recommend), or you do already have a functional pkg-config.exe, then the first thing I'd want to see is the full output of your
perl Makefile.PL... step.
Further on down the track, I formed the opinion that Strawberry's propensity to produce dlls named with a terminating ".xs.dll" didn't play well with ExtUtils::Depends, thus creating additional hoops to negotiate when building (eg) Cairo.
But I never proved to myself that this opinion was correct - and, anyway, I was using my own builds of perl that built dlls without the ".xs" component in their names.
Still, I'd suggest building your own perl (which is quite easy) if you want to build the Gtk stuff, rather than using Strawberry Perl - because doing so simply eliminates one potential difficulty.
Cheers,
Rob