Tweaking autotools-based buildsystem for W32 compatibility

LRN lrn1986 at gmail.com
Tue Mar 18 08:54:01 EDT 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As some of you (who's been on #pidgin) may remember, i've mostly
ignored the usual building instructions, which assume the use of
pre-generated Makefile.mingw makefiles and pre-built binaries for
dependencies.

Anyway, i've successfully built 2.x.y and 3.0.0 on W32 with autotools,
which resulted in a heap of patches on my side (~44 for 3.0.0, ~48 for
2.x.y). How do i go about submitting them? Usually projects frown upon
attaching so many patches to one bugreport/issue/ticket, but creating
40+ tickets (maybe 10+, if i group patches intelligently; that's still
a bit too much, IMO) seems like a bad move too. Especially since some
patches may not be committable as-is (i'm not always patient enough to
come up with a change that fixes the issue for me and does not break
anything for everyone else).

- -- 
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQEcBAEBAgAGBQJTKEHpAAoJEOs4Jb6SI2CwCfUH/3Jp5OiSwpka0WjxNp/RzxiW
Laz5ypM1N7QsoE+KXZJ1b01adLtLaXXixAQclUIyiKN31+biFnWx9M8AoFVuOW7S
TBAAWg0GOldkcb0S5w8MDEBGvZZ7plDl9GWWgIytyG1zKw1Wp6i/M/IIRq4owmpA
QiS4AQ+jEx7ZOkNsDZ/GCnF0QjW+0mqNXIfa7r161VkX8992ci1goqumgM+e5nfL
LjWOCN+pFavbJ7oz6Zqsmxk16TXLuUxF01j9NsMgrU8JI/7AXgmq31afl+Q0adRg
WwPpu6bH9BWmICl62AzaIVF6AoEKQQqmJsel7tS8W31ZcZ6ye825Qzmm6E/F//o=
=Ylxh
-----END PGP SIGNATURE-----



More information about the Devel mailing list