ok after some further research I have found this page (probably the one you @SGaist were referring to) https://forums.developer.apple.com/thread/9233.

As you mentioned, it seems that DYLD_* variables have been disabled (they are ignored) since El Capitan because of a new feature called System Integrity Protection (SIP). According to Apple Developer website, debugging can be happily performed only by Xcode (although I haven't tried it yet). What about Qt? Will 5.5.1 or 5.6 allow debugging on El Cap with SIP?

I read on another page SIP can be disabled in Recovery mode. Anyway, I am not keen at hacking my own system... the alternative is to wait for the next version of Qt and hope for a solution. Unsure what to do for now, in the meanwhile I am stuck! Grrr

UPDATE: I ended up disabling SIP following the following step:

Enter Recovery mode (Cmd+R on startup) Open Terminal csrutil disable; reboot

Now debugging went back to normality!

My only doubt is that when i do csrutil status, I receive the following message:

"System Integrity Protection status: enabled (Custom Configuration).

Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state."

Not very reassuring uh? (and why is that still saying SIP enabled?)

@shav
Yes this seemed to solve my problem too, but only to the next roadblock.
The log seems to show the deployment of the modules, Log:
Log: Deploying QML imports
Log: Application QML file search path(s) is ("/Users/guymcnally2/UncutDev/Qt/build-celebrifyNewSolution-iphonesimulator_clang_Qt_5_5_1_for_iOS-Debug/../celebrify/qml")
Log: Deploying QML import "QtQuick"
Log:
Log: Deploying QML import "QtQuick.Controls"
Log:
Log: Deploying QML import "QtQuick.Window"
Log:
Log: Deploying QML import "QtQuick"
Log:
Log: Deploying QML import "QtQuick.Controls"
Log:
Log: Deploying QML import "QtQuick.Window"
Log:
Log: Deploying QML import "QtQuick"
Log:
Log: Deploying QML import "QtQuick.Controls"
Log:
Log: Deploying QML import "QtQuick.Controls.Styles"
Log:
Log: Deploying QML import "QtQuick.Controls.Private"
Log:
Log: Deploying QML import "QtQuick.Layouts"
Log:
Log: Deploying QML import "com.uncutvideo.qmlcomponents"
Log: Skip import: name or path is empty
Log:
Log: Deploying QML import "QtQuick.Dialogs"
Log:
Log: Deploying QML import "Qt.labs.folderlistmodel"
Log:
Log: Deploying QML import "Qt.labs.settings"
Log:
Log: Deploying QML import "QtQuick.Dialogs.Private"
Log:
Log: Deploying QML import "QtQuick"
Log:
Log: Deploying QML import "QtQuick.Layouts"
Log:
Log: Deploying QML import "QtQuick.Controls.Styles"
.......
Log: Deploying QML import "QtQuick.PrivateWidgets"
Log:
21:02:51: The process "/Applications/Qt/Qt5.5.1/5.5/clang_64/bin/macdeployqt" exited normally.
21:02:51: Elapsed time: 00:03. but when the application launches, I get the output,
qrc:/qml/MainPanelLandscape.qml:3:1: module "QtQuick.Window" is not installed
qrc:/qml/MainPanelLandscape.qml:4:1: module "QtQuick.Controls.Styles" is not installed
qrc:/qml/MainPanelLandscape.qml:5:1: module "QtQuick.Controls.Private" is not installed
qrc:/qml/MainPanelLandscape.qml:6:1: module "QtQuick.Layouts" is not installed
qrc:/qml/MainPanelLandscape.qml:1:1: module "QtQuick" is not installed
qrc:/qml/MainPanelLandscape.qml:2:1: module "QtQuick.Controls" is not installed

so the end result is the same.
Any suggestions what to try next?

@SGaist

Thank you very much, I used the work-around they proposed
(storing a copy of the certificate in the local resources of the app & adding that to the default CACertificate list before opening the socket)
I'm afraid this won't be a clean long term solution though (the certificate will stay valid for a while, but eventually expires I guess).
If anyone has any idea's for a more clean/permanent solution I'm very much open to suggestions.
In the mean time this will have to do.
Thanks again, I appreciate the comment

The latest development is that I had over 254 files open at once. No wonder nobody else had encountered this.

@maximo Depending on needs of your application you may create a customized build of QtWebKit without some features, which may substantially reduce binary size.

@SGaist
Thank you for the reply, SGaist! I'll do it.

@SGaist Thanks! I'll waiting for next release!

Issue created at QTBUG-47390

Hi,

Out of curiosity, can you describe what your application does that it needs all of these elements hidden ?

@mcosta Thanks mcosta

Yes, indeed I can show website over https with WebEngine, even though it still show those warning messages. As documented here, Web Kit will be deprecated in Qt version 5.5+, so I'll switch to use WebEngine then.

For those who feel annoyed with the warning messages, you could suppress them by calling following method in your main()

QLoggingCategory::setFilterRules("qt.network.ssl.w arning=false");

or by setting environment variable

QT_LOGGING_RULES=qt.network.ssl.warning=false

ok finally:

modifying Qt/5.3/clang_64/mkspecs/macx-clang/qmake.conf

this way:

#QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.6
QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.7

did the job.

just in case anybody needs this again. seems easy afterwards -.-

Finally I found the problem. My Info.plist file was missing CFBundleIdentifier. After I added it, application was able to register in Notification Center.

<key>CFBundleIdentifier</key> <string>org.notifytestosx.app</string>

This commit has required fix:
https://github.com/beemaster/osxnotifytest/commit/fa4154eebf9ffa51f9f9e5de5d12239c18d02370

Hi and welcome to the devnet,

I use protobuf too (in Windows, Linux and OSX).
In our OSX environment we build protobuf with

$PROTOBUF_SRC_DIR/configure --silent --prefix=$PREFIX --disable-shared --enable-dependency-tracking=no

@devbrs You certainly must check if taglib is null. And you must use toUTF8() instead of toAscii().

The last problem is that some of the string conversion functions in TagLib don't appear to work with the QString conversion functions.

Namely the functions that create c++ string and wstring objects:

QString::fromStdString(tag->title().to8Bit()); QString::fromStdWString(tag->title().toWString());

The functions that return c style string pointers do work:

QString::fromWCharArray(tag->title().toCWString()); QString(tag->title().toCString(true));

Now, why the string functions work on Linux and not on the Mac, I don't know. Perhaps you could delve into it.

Hi and welcome to devnet,

Looks like you hit QTBUG-42708 which is related to QTBUG-36175 that's in progress