Mercurial > pidgin.yaz

annotate README.mingw @ 32635:63e7d226b760

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Re-arrange these doxygen comments. For comments longer than a few words, putting the comment before the variable like this seems cleaner than trying to cram it on the same line as the variable and using lots of crazy indentation. Anyone have a strong opinion either way?
author Mark Doliner <mark@kingant.net>
date Sun, 18 Sep 2011 20:18:33 +0000
parents 416a125b66ac
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
16209
416a125b66ac Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents: 16039
diff changeset
1 How to build Pidgin for Windows using MinGW
416a125b66ac Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents: 16039
diff changeset
2 =============================
3630
9682c0e022c6 [gaim-migrate @ 3753]
Rob Flynn <gaim@robflynn.com>
parents:
diff changeset
3
16209
416a125b66ac Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents: 16039
diff changeset
4 For the latest build instructions, please refer to:
3630
9682c0e022c6 [gaim-migrate @ 3753]
Rob Flynn <gaim@robflynn.com>
parents:
diff changeset
5
16209
416a125b66ac Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents: 16039
diff changeset
6 http://developer.pidgin.im/wiki/BuildingWinPidgin