Re: [PHP-GTK] php_curl

[email protected] ("Steph Fox")
Newsgroups php.gtk.general
Organization Zend Technologies
Message-ID <08fa01c8046b$0d7ff300$e6dfc350@foxbox>
Hi,

You should be able to pick up everything you need from the PHP museum - 
http://museum.php.net/.

HTH,

- Steph

----- Original Message ----- 
From: "NOT_Skeletor" <[email protected]>
To: <[email protected]>
Sent: Monday, October 01, 2007 9:21 PM
Subject: [PHP-GTK] php_curl


>
> Everyone was so helpful with my last problem, I thought I'd stick this one
> up.
> The chat app requires talking to the main server. I do this with REST 
> calls
> which necessarily requires curl to function.
> The php-gtk install I took from the http://gtk.php.net for win32 doesn't
> have this as a module. So, I grabbed the binaries of php.5.2.4 which does.
> That works great, but of course, it doesn't have the php_gtk2.dll
>
> I tried to "marry" the two of them, but came across a stumbling block when
> trying to load the php_gtk.dll:
>
> Module compiled with module API=20060613, debug=0, thread-safety=0
> PHP compiled with module API=20060613, debug=0, thread-safety=0
> These options need to match
>
> The same thing (but in reverse) happened when I tried to copy the
> php_curl.dll to the php-gtk build.
>
> So, how can I get cURL functionality into php-gtk? I have never compiled
> source to a windows binary (I'm a Linux guy, but I have to build this to
> deploy on Windows-based machines) so I'm not sure how to do it. I assume
> this is what is needed to get the thread-safety issue resolved. OR is
> someone able to compile this for me? I would be ever so grateful :)
> -- 
> View this message in context: 
> http://www.nabble.com/php_curl-tf4550784.html#a12986884
> Sent from the Php - GTK - General mailing list archive at Nabble.com.
>
> -- 
> PHP-GTK General Mailing List (http://gtk.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.