Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Configure "qtnamespace" flags?
Qt 6.11 is out! See what's new in the release blog

Configure "qtnamespace" flags?

Scheduled Pinned Locked Moved Installation and Deployment
3 Posts 2 Posters 4.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    nonot1
    wrote on last edited by
    #1

    Hello,

    The instructions for building the Qt / Eclipse integration says that Qt must be configured with:

    "./configure -qtnamespace QtCppIntegration -qtlibinfix CppIntegration"

    I see the man page at http://doc.qt.nokia.com/4.7-snapshot/configure-options.html , but I still don't understand:

    What exactly does this do?

    Why/when I would need to use these flags in other cases?

    Could regular Qt-based code still use the Qt built like this?

    Why, in this case, the particular names "QtCppIntegration" and "CppIntegration"?

    Thank you

    1 Reply Last reply
    0
    • S Offline
      S Offline
      sigrid
      wrote on last edited by
      #2

      qtnamespace compiles Qt into a namespace and qtlibinfix modifies the names of the Qt dlls. For example: qtlibinfix renames all the Qt dlls with the infix you have chosen, for example to QtGuiCppIntegration.dll and qtnamespace wraps all of the Qt code in the namespace QtCppIntegration

      You can see an example of another usecase for qtlibinfix "here ":http://developer.qt.nokia.com/faq/answer/how_can_i_have_several_qt_versions_installed_under_winntsystem32

      Yes

      The reason there is a difference between the naming of the options "QtGuiCppIntegration" and "CppIntegration" is simply that if qtlibinfix had the option "QtCppIntegration then the resulting dll names would be e.g "QtGuiQtCppIntegration" which does not look as nice as QtGuiCppIntegration

      1 Reply Last reply
      0
      • N Offline
        N Offline
        nonot1
        wrote on last edited by
        #3

        Thank you, sigrid.

        Three followup questions:

        You said that code that was written for normal Qt can be used with Qt built like this, but I assume that some changes must be made to some makefile /.pro file... Correct? If so, is there a simple example somewhere?

        Does anyone know why the Eclipse integration needed these flags?

        For the Eclipse integration, was the choice of "CppIntegration" arbitrary, or was that exact name needed to integrate with some other library?

        Thank you

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved