[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pidgin-devel
Subject:    Re: Summer of Code
From:       "Daniel Atallah" <daniel.atallah () gmail ! com>
Date:       2008-03-26 15:51:36
Message-ID: da6ae2570803260851w57fc6746ra2ab7792c7c79a0e () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2008/3/26 John Bailey <rekkanoryo@rekkanoryo.org>:

> I've done a bit of digging and determined that the major hurdle here will
> probably be gettext.  Glib provides Visual Studio 2005 project support
> files
> that need only minor tweaking for include paths, but it of course requires
> gettext.  Gettext no longer supports Visual Stuido at all, instead
> expecting the
> use of Cygwin and MinGW.


Presumably the solution to this is to simply use the mingw-built gettext.
There shouldn't be any issues mixing CRTs with something like that.

-D

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">2008/3/26 John Bailey &lt;<a \
href="mailto:rekkanoryo@rekkanoryo.org">rekkanoryo@rekkanoryo.org</a>&gt;:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> I&#39;ve done a bit of digging and determined that \
the major hurdle here will<br> probably be gettext. &nbsp;Glib provides Visual Studio \
2005 project support files<br> that need only minor tweaking for include paths, but \
it of course requires<br> gettext. &nbsp;Gettext no longer supports Visual Stuido at \
all, instead expecting the<br> use of Cygwin and MinGW. \
&nbsp;</blockquote><div><br>Presumably the solution to this is to simply use the \
mingw-built gettext.&nbsp; There shouldn&#39;t be any issues mixing CRTs with \
something like that.<br><br>-D<br></div></div>



_______________________________________________
Devel mailing list
Devel@pidgin.im
http://pidgin.im/cgi-bin/mailman/listinfo/devel


[prev in list] [next in list] [prev in thread] [next in thread]