glib-compile-resources using strings breaks building e.g. GTK+ on MS Visual C, which limits strings to 65535 chars
#1489 (closed) / 0d685b49 changed glib-compile-resources
to use strings instead of arrays of bytes.
There's a big problem with that: MSVC has a hard limit of 65535 character long strings and no way that I can find to get around this. A user on #gtk+
reported that it's impossible to build GTK+ master
due to this, and I presume GTK+ 3 doesn't have smaller enough resources that it would fare any better.
Given the lack of ways to make MSVC accept the strings, it seems the old method needs restored, at least for Windows. This is quite urgent, not only for GTK+, but also if we presume it's likely that other users of GLib with MSVC will have their projects broken by this.
If no one has/wants an automagical patch that can do the new thing where appropriate and the old thing where not, then the change should just be reverted as increased speed on other compilers isn't worth totally breaking on MSVC.