oneAPI TBB & Qt

44 views

Skip to first unread message

Colin Doncaster

unread,

Mar 10, 2025, 3:04:34 PMMar 10

to vfx-platform-discuss

Hi all

I’ve noticed that oneAPI TBB and Qt don’t play well together as oneTBB’s new profiling.h defines emit which has a keyword conflict with Qt’s emit.

The Qt docs mention the QT_NO_KEYWORDS define that can be used to avoid these being defined at https://doc.qt.io/qt-6/signalsandslots.html#using-qt-with-3rd-party-signals-and-slots but that also assumes all source in a project moves to using Q_EMIT/SIGNALS/SLOTS etc.

There's also some discussion at https://github.com/uxlfoundation/oneTBB/issues/547

After some judicial refactoring by isolating headers etc. I was able to get it to work but thought I'd provide a heads up for others moving to the new oneTBB release as I couldn't find any previous discussions about this.