On Thu, 2014-01-09 at 12:10 -0200, Otavio Salvador wrote:
> On Thu, Jan 9, 2014 at 9:16 AM, Phil Blundell <[email protected]> wrote:
>
> Although libsoup did use to support direct usage of libproxy,
> it hasn't
> done so for some time. Worse, if libsoup depends on libproxy
> then it
> is impossible to build libproxy against webkit since webkit
> itself
> depends on libsoup in some configurations. Fix this by
> removing the
> extraneous entry from DEPENDS.
>
> Signed-off-by: Phil Blundell <[email protected]>
>
>
>
> Does it need a --disable-libproxy or so?
No. See the (old) NEWS:
Changes in libsoup from 2.33.90 to 2.33.92:
* LIBSOUP NO LONGER DEPENDS ON GCONF OR LIBPROXY.
(see below).
* Updated SoupProxyResolverGNOME to be based on
SoupProxyResolverDefault, but explicitly requesting
the
"gnome" GProxyResolver if it is available [#625898],
and
removed the old code that used GConf and libproxy
directly.
p.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
