Re: [Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

I am building qt from a couple of different scripts so it would be great to be able to have them work on first run. > On Jun 21, 2019, at 8:50 PM, Patrick Stinson wrote: > > My config.log did not contain the string “std-atomic64.” It did report that > it could not find libatomic. Deleting

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

On 21/6/19 9:13 pm, Elvis Stansvik wrote: Den fre 21 juni 2019 09:13Kai Köhne > skrev: For the time being, it seems you've to execute the codesign call yourself. This is what I've done at work to prepare our builds for this. We use CMake though and we're

Re: [Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

On Friday, 21 June 2019 10:35:36 PDT Patrick Stinson wrote: > #define QT_FEATURE_std_atomic64 -1 Can you check the config.log in the top-level dir to see what how the std- atomic64 test failed? If you don't see that in the config.log, remove config.cache and rerun configure (./config.status) --

Re: [Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

Every time I had this error recently it's because I cleaned my build directory via rm -rf * which did not remove the hidden .qmake.cache files in there which then thoroughly destroys any attemptto rebuild qt in this directory. Maybe it can help ? (it was the exact same symptoms in any case) Best,

Re: [Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

#define QT_FEATURE_std_atomic64 -1 > On Jun 21, 2019, at 9:32 AM, Thiago Macieira > wrote: > > src/corelib/qtcore-config.h ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest

Re: [Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

On Friday, 21 June 2019 10:00:45 PDT Patrick Stinson wrote: > thread/qatomic.cpp:1624:4: error: "Q_ATOMIC_INT64_IS_SUPPORTED must be > defined on a 64-bit platform" The macro is defined by this block in qatomic_cxx11.h: #if QT_CONFIG(std_atomic64) template<> struct QAtomicOpsSupport<8> { enum {

[Interest] Q_ATOMIC_INT64_IS_SUPPORTED: Qt Compile errors on macOS

(NOTE: I have started a new thread about this from an old one incorrectly associating this problem with “make -jn”) I am having a hard time pinning down the source of this error. I am getting it sporadically on Qt-5.12.0 - Qt-5.13.0. using make -jn flags or not using make -jn flags doesn’t

[Interest] Accessibility - Different output to braille display and speech?

Is it possible to write a Qt application which passes two strings to a screenreader (I'm using NVDA), such that the first string is what is displayed on a Braille display, and the second string is spoken. The reason is that I have a calendar application, with entries on the screen in the form:

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

Den fre 21 juni 2019 15:33Michael Jackson skrev: > *From: *Interest on behalf of Elvis > Stansvik > *Date: *Friday, June 21, 2019 at 7:14 AM > *To: *Kai Köhne > *Cc: *Qt Interest > *Subject: *Re: [Interest] notarizing builds for Mac - enabling hardened > runtime > > > > Den fre 21 juni 2019

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

Den fre 21 juni 2019 15:39Konstantin Tokarev skrev: > > > 21.06.2019, 16:36, "Michael Jackson" : > > Apple, sigh, I can understand and sympathize requiring signed builds, > but this mandatory "virus scanned by Apple" is a little silly. As a user I > trust the virus scanner I pick myself more

Re: [Interest] Problem with cv::Mat grayscale to QImage

On Friday, 21 June 2019 15:52:55 CEST Jason H wrote: > It seems that there is some word/dword/byte-alignment magic going on and the > skew is proportional to that. Yes, scan-lines are 32bit aligned. So for non-32bit images we add padding to each line to make them align. 'Allan

Re: [Interest] Problem with cv::Mat grayscale to QImage

It seems that there is some word/dword/byte-alignment magic going on and the skew is proportional to that.    Sent: Friday, June 21, 2019 at 9:40 AM From: "Jason H" To: "René Hansen" Cc: "interestqt-project.org" Subject: Re: [Interest] Problem with cv::Mat grayscale to QImage That indeed

Re: [Interest] Problem with cv::Mat grayscale to QImage

That indeed seems to be the case. But this is very interesting for Grayscale. RGB888 is fine. Maybe this is more a OpenCV question, why would the BPL not equal pixels per line?   Many thanks to all who replied.   Sent: Thursday, June 20, 2019 at 5:33 PM From: "René Hansen" To: "Jason H" Cc: 

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

21.06.2019, 16:36, "Michael Jackson" : > Apple, sigh, I can understand and sympathize requiring signed builds, but > this mandatory "virus scanned by Apple" is a little silly. As a user I trust > the virus scanner I pick myself more than some blackbox process on Apple HQ > servers. To be

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

From: Interest on behalf of Elvis Stansvik Date: Friday, June 21, 2019 at 7:14 AM To: Kai Köhne Cc: Qt Interest Subject: Re: [Interest] notarizing builds for Mac - enabling hardened runtime Den fre 21 juni 2019 09:13Kai Köhne skrev: > -Original Message- > From: Interest On

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

Den fre 21 juni 2019 09:13Kai Köhne skrev: > > -Original Message- > > From: Interest On Behalf Of Hamish > > Moffatt > > Sent: Friday, June 21, 2019 8:42 AM > > To: Qt Interest > > Subject: [Interest] notarizing builds for Mac - enabling hardened runtime > > > > Apple says that all

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

> -Original Message- > From: Interest On Behalf Of Hamish > Moffatt > Sent: Friday, June 21, 2019 8:42 AM > To: Qt Interest > Subject: [Interest] notarizing builds for Mac - enabling hardened runtime > > Apple says that all apps will need to be notarized (viewed) by them to be run > on

Re: [Interest] notarizing builds for Mac - enabling hardened runtime

On Fri, Jun 21, 2019 at 9:42 AM Hamish Moffatt wrote: > > Apple says that all apps will need to be notarized (viewed) by them to > be run on macOS 10.15 once released. > Apps must have the hardened runtime enabled in Xcode before they can be > notarized. > Is there any way to get qmake to enable

[Interest] notarizing builds for Mac - enabling hardened runtime

Apple says that all apps will need to be notarized (viewed) by them to be run on macOS 10.15 once released. Apps must have the hardened runtime enabled in Xcode before they can be notarized. Is there any way to get qmake to enable that project option? Hamish