Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. CMake Desktop projects, linked with system's Qt 4.8.0, can't run in the QtCreator 2.4.1 which built them
Forum Updated to NodeBB v4.3 + New Features

CMake Desktop projects, linked with system's Qt 4.8.0, can't run in the QtCreator 2.4.1 which built them

Scheduled Pinned Locked Moved Qt Creator and other tools
3 Posts 2 Posters 4.2k 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.
  • R Offline
    R Offline
    RolandH
    wrote on last edited by
    #1

    Ctrl+R:

    symbol lookup error: ... undefined symbol: _ZN16QCoreApplicationC1ERiPPci

    I can't see anywhere (much less control) which Qt version QtCreator is trying to dynamically link here, but one can assume it is it's enclosed 4.7.4. The executable is running flawless outside of QtCreator.

    Is there any workaround until the build of QtCreator catches up with the actual Qt version again?

    The last version of Creator, 2.4.0, didn't have that problem.

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on last edited by
      #2

      Qt Creater fully supports Qt 4.8 and even Qt 5. No need to wait for it to catch up:-)

      The problem is that Qt Creator has no idea which libraries, etc. are getting used when using CMake... the configuration files there are basically impossible to parse correctly. So you need to do some manual tweaking to the environment you work in there.

      I suggest checking Projects->Run Settings. Go over the environment used to run the project there and compare it to your "normal" environment outside Qt Creator. The PATH and LD_LIBRARY_PATH (or whatever influences the library search pathes on your platform) are of special importance here.

      I hope this helps:-)

      1 Reply Last reply
      0
      • R Offline
        R Offline
        RolandH
        wrote on last edited by
        #3

        Yes, that helped, thanks.

        The runtime environment looked so much unchanged from my normal one, that I didn't spot LD_LIBRARY_PATH in it. Well hidden, indeed! ;-)

        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