Fine with me too. I was only sharing this in case it was useful to someone else. I would much prefer using MingW anyway...
DRC wrote: > I would tend to agree. Also, we're going to start building with MinGW > at some point in the not-so-distant future. > > Pierre Ossman wrote: >> I'd prefer if this was backed out. As I said, this just hides the >> obvious unicode handling errors without actually verifying that the >> rest of the code can handle it. We would need a huge audit to remove >> all references to the "normal" string handling functions for that*. >> >> * Something which I don't support. We should be using UTF-8 for >> unicode, not UTF-16. >> >> Rgds > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
