<![CDATA[Using glib and gtk with Qt]]>I have a common project which is developed using glib, gtk and some other libraries. I will use this common project's headers&source files in my project. I added required PKGCONFIGs to my .pro file. It builds succesfully. But when i include header files of common project to my project and try to build project:

/usr/include/qt6/QtCore/qtmetamacros.h:45:20: error: expected unqualified-id before ‘public’
   45 | # define Q_SIGNALS public QT_ANNOTATE_ACCESS_SPECIFIER(qt_signal)
      |                    ^~~~~~
/usr/include/qt6/QtCore/qtmetamacros.h:41:22: note: in expansion of macro ‘Q_SIGNALS’
   41 | #     define signals Q_SIGNALS
      |                      ^~~~~~~~~
/usr/include/glib-2.0/gio/gdbusintrospection.h:157:25: note: in expansion of macro ‘signals’
  157 |   GDBusSignalInfo     **signals;
      |                         ^~~~~~~
/usr/include/qt6/QtCore/qtmetamacros.h:45:20: error: expected unqualified-id before ‘public’
   45 | # define Q_SIGNALS public QT_ANNOTATE_ACCESS_SPECIFIER(qt_signal)
      |                    ^~~~~~
/usr/include/qt6/QtCore/qtmetamacros.h:41:22: note: in expansion of macro ‘Q_SIGNALS’
   41 | #     define signals Q_SIGNALS
      |                      ^~~~~~~~~
/usr/include/gtk-3.0/gtk/gtkbindings.h:103:21: note: in expansion of macro ‘signals’
  103 |   GtkBindingSignal *signals;
      |                     ^~~~~~~

I saw a thing CONFIG += no_keywords, that can maybe solve the problem(i didnt try it yet) but i will need to change all signal, slot, emit keywords in my project. Any better way? And why this happening? Because of glib use same keywords or something?

]]>https://forum.qt.io/topic/142146/using-glib-and-gtk-with-qtRSS for NodeTue, 06 Oct 2026 17:53:47 GMTThu, 12 Jan 2023 08:35:43 GMT60<![CDATA[Reply to Using glib and gtk with Qt on Fri, 13 Jan 2023 07:11:28 GMT]]>By the way easiest solution i found is: adding #undef signals before glib includes, and after it #define signals again.

]]>https://forum.qt.io/post/743689https://forum.qt.io/post/743689Fri, 13 Jan 2023 07:11:28 GMT<![CDATA[Reply to Using glib and gtk with Qt on Fri, 13 Jan 2023 04:30:05 GMT]]>@jsulm Thank you, that was what i found. So only easy option is converting signal slots to their macro names.

]]>https://forum.qt.io/post/743674https://forum.qt.io/post/743674Fri, 13 Jan 2023 04:30:05 GMT<![CDATA[Reply to Using glib and gtk with Qt on Fri, 13 Jan 2023 04:28:29 GMT]]>@stryga42 I wont use gtk for my UI, but the common project includes gtk, and uses it in inner test programs. I am not sure how can i isolate them. Thanks anyway.

]]>https://forum.qt.io/post/743673https://forum.qt.io/post/743673Fri, 13 Jan 2023 04:28:29 GMT<![CDATA[Reply to Using glib and gtk with Qt on Thu, 12 Jan 2023 17:31:56 GMT]]>@masa4 To add to @stryga42 take a look at https://doc.qt.io/qt-5/signalsandslots.html#using-qt-with-3rd-party-signals-and-slots

]]>https://forum.qt.io/post/743629https://forum.qt.io/post/743629Thu, 12 Jan 2023 17:31:56 GMT<![CDATA[Reply to Using glib and gtk with Qt on Thu, 12 Jan 2023 17:28:47 GMT]]>It seems that the token signals is used as a variable name in glib and defined as a macro in Qt6. Since macro substitution happens very early there is not much you can do.
Maybe you can isolate gtk and Qt so that Qt includes (which provide the annoying macro definition) are never processed before gtk includes happen.
General remark: Mixing direct gtk and Qt in one GUI may create "strange" results - I ran into such a problem years ago, see this post. So it may be a good idea to keep things separated anyway.

]]>https://forum.qt.io/post/743628https://forum.qt.io/post/743628Thu, 12 Jan 2023 17:28:47 GMT