From 8a6f52bf83f7f8e97e4eed7bafbcdfd85a5a5bab Mon Sep 17 00:00:00 2001 From: Christophe Giboudeaux Date: Tue, 17 Nov 2020 13:44:57 +0100 Subject: Remove obsolete warnings The libproxy issue was fixed 4 years ago and the related Qt and libproxy bug reports were also closed long ago. Change-Id: I5af18f1eaaffb8d33556ab94ca1759959a2c272d Reviewed-by: Alexandru Croitor --- src/network/configure.json | 5 ----- 1 file changed, 5 deletions(-) (limited to 'src/network/configure.json') diff --git a/src/network/configure.json b/src/network/configure.json index 835e449e5d..3234fa6474 100644 --- a/src/network/configure.json +++ b/src/network/configure.json @@ -453,11 +453,6 @@ library names through OPENSSL_LIBS. For example: OPENSSL_LIBS='-L/opt/ssl/lib -lssl -lcrypto' ./configure -openssl-linked" - }, - { - "type": "warning", - "condition": "features.libproxy && input.qt_namespace == ''", - "message": "Some of libproxy's plugins may use incompatible Qt versions. Some platforms and distributions ship libproxy with plugins, such as config_kde4.so, that are linked against old versions of Qt; and libproxy loads these plugins automatically when initialized. If Qt is not in a namespace, that loading causes a crash. Even if the systems on which you build and test have no such plugins, your users' systems may have them. We therefore recommend that you combine -libproxy with -qtnamespace when configuring Qt." } ], -- cgit v1.2.3