Re: libpurple, the nullclient and AIM

Oops, after a little more investigation I realized that whenever I imported the WIN32 def'd code, nullclient wasn't actually compiling, so I had never *actually* tested that change!  Once I got it to compile with the win32 specific code in it, AIM worked like a charm.  Thanks so much for your help!  The trick was including win32/win32dep.h, which had declarations for some of the functions used in the win32 specific code.

---

From: Jeremy Trammell - Setaris jeremy.trammell@...

To: Daniel Atallah daniel.atallah@...

CC: support@... support@...

Sent: 07/07/2009 9:14:22 AM -0400

Subject: libpurple, the nullclient and AIM

Oh yes, sorry, I've been playing around with this for so long now I forgot about that!  Yes, I've tried including the WIN32 code with no change in the results (double checked it right now just to be sure).  I still get to "Username sent" and then nothing else for AIM.

Jeremy Trammell Chief Technology Officer		509 East 87th St. #1W New York, NY 10128
Setaris Corporation		cell +1.518.331.5180
www.setaris.com		fax +1.646.786.4370

INTELLIGENT SOFTWARE

---

---

From: Daniel Atallah daniel.atallah@...

To: Jeremy Trammell - Setaris jeremy.trammell@...

CC: support@... support@...

Sent: 07/07/2009 8:41:37 AM -0400

Subject: libpurple, the nullclient and AIM

On Tue, Jul 7, 2009 at 8:06 AM, Jeremy Trammell -
Setarisjeremy.trammell@... wrote:
  

glib_input_add() looks identical to pidgin_input_add() to me.  I'm pretty
sure they compile to the same code.
    

They don't.  Look at the #ifdef _WIN32 stuff.

-D
  

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support

_______________________________________________
Support@... mailing list
Want to unsubscribe?  Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support