MSVC Portability

John Bailey rekkanoryo at
Fri Apr 5 23:22:53 EDT 2013

On 04/05/2013 01:07 PM, Zoltán Sólyom wrote:
> On 13/04/05 18:40, Richard Laager wrote:
>> For your libpurple changes, maybe upload a fork of the pidgin repository
>> to
> I don't want to fork libpurple. Maintaining that would be a pain. Most of the
> changes consist of commenting out includes not in VS. There are one or two other
> things apart from that, but nothing difficult. (And I could probably include
> almost all of the fixes as parameters in the VS project files.) I only want to
> upload the VS projects for libpurple, a text file about where to put them once
> someone got the pidgin source, what else to download, and maybe some lines about
> what things were difficult when writing the first program.

A fork of the repository is not necessarily a fully-fledged fork of
Pidgin/Finch/libpruple.  I believe all Richard was suggesting was that you check
out a copy of the repository, add your Visual Studio solution files to that
repository, and publish it on (as a "fork," which is essentially
just a copy you "own").  Given that you're aiming to keep your changes minimal,
maintenance would be minimal--pull from our repository occasionally, merge if
necessary, and push to yours; any necessary merges would likely be completely
automatic or require only the smallest of efforts.  Additionally, you could use
the fork to incrementally develop your solution files, then submit a pull
request to us when they're ready--I believe we should support compiling on
Visual Studio, so I would advocate shipping known-working solution files for
that purpose.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Devel mailing list