On Monday, 11 March 2019 18:23:37 PDT Giuseppe D'Angelo via Interest wrote:
> Il 12/03/19 02:11, Allan Sandfeld Jensen ha scritto:
> >> The problem is not the GCC version. It's the set of libraries provided by
> >> the old distribution.
> >
> > And I guess he could still build his own packages. Th
Il 12/03/19 02:11, Allan Sandfeld Jensen ha scritto:
The problem is not the GCC version. It's the set of libraries provided by
the old distribution.
And I guess he could still build his own packages. The libraries would just
use bundled qt copies if too old. Only the prebuilt packages have highe
On Dienstag, 12. März 2019 02:02:44 CET Thiago Macieira wrote:
> On Monday, 11 March 2019 04:14:02 PDT Bill Crocker wrote:
> > If you can build with GCC 4.8 on "Generic Linux" why does
> > RHEL7 require GCC 5.3.1
>
> The problem is not the GCC version. It's the set of libraries provided by
> the o
On Monday, 11 March 2019 13:41:11 PDT Konstantin Shegunov wrote:
> Hello,
> Is there a current recommended way of catching exceptions before they
> unwind through the event loop?
Yes: just catch them before letting them come back to any Qt function. You
should treat all your slots and event hand
On Monday, 11 March 2019 04:14:02 PDT Bill Crocker wrote:
> If you can build with GCC 4.8 on "Generic Linux" why does
> RHEL7 require GCC 5.3.1
The problem is not the GCC version. It's the set of libraries provided by the
old distribution.
--
Thiago Macieira - thiago.macieira (AT) intel.com
S
On Monday, 11 March 2019 03:56:59 PDT René J.V. Bertin wrote:
> One hurdle: my distribution uses dbus 1.6.x which lacks at least 1 function
> required by libQt5Dbus. I don't really want to risk rolling my own upgrade
> for that. So instead I installed dbus 1.12.12 into my usual /opt/local
> paralle
Hello,
Is there a current recommended way of catching exceptions before they unwind
through the event loop? I want this for "debug purposes" only. I have few
methods that throw and I (think I) catch (all of) my exceptions before they
reach the event loop, but I wanted to be sure I hadn't forgot
Hello,
Is there a current recommended way of catching exceptions before they
unwind through the event loop? I want this for "debug purposes" only. I
have few methods that throw and I (think I) catch (all of) my exceptions
before they reach the event loop, but I wanted to be sure I hadn't
forgotten
from https://wiki.qt.io/New_Features_in_Qt_5.13 I noticed this:
Qt Bluetooth
* Removed need for pairing on Windows to discover and connect
Does this mean it is possible to connect with Bluetooth LE Devices where
no pairing is needed from default binaries ? (Windows 10, MSVC2017)
thx
ekke
___
> On 8 Mar 2019, at 11:29, maitai wrote:
>
> Yes with anchors.fill:parent, Pressed/Released works only if the mouse is
> exactly on the line, while hover seems to use the bounding rect of the
> polyline...
>
> But anyway with containmentMask: polyline, all is OK and hover occurs only
> exact
If you are installing onto RHEL 6 as indicated in the case settings then this
is not supported
which would explain why it is having this problem, Qt was built on RHEL 7.4 for
Qt 5.12 as indicated here:
https://doc.qt.io/qt-5/supported-platforms.html
so you will need to upgrade in order
Hi,
I wanted to test something against a newer Qt version than my customised 5.9.7
build so I used the official installer to get 5.12.1 and wrote a little wrapper
that sets up LD_LIBRARY_PATH and QT_PLUGIN_PATH appropriately to run existing
binaries against this Qt version.
One hurdle: my dist
12 matches
Mail list logo
