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. [Qt Creator] How to *not* require user to "Configure Project" on open Qt project ( *.pro) file before building?
Forum Updated to NodeBB v4.3 + New Features

[Qt Creator] How to *not* require user to "Configure Project" on open Qt project ( *.pro) file before building?

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

    Under Qt5.1 Windows, opening a Qt project ( *.pro) in Qt Creator 2.7.2 requires user to first "Configure Project" before he can build. Is there a way to disable this Qt Creator 2.7.2 behavior and default to a configuration using the default kit? Or perhaps a way to assign qmake variables in the Qt project ( *.pro) to pre-configure project?

    I guess I am trying to reproduce our Qt4 Linux environment where only the Qt project ( *.pro) was version controlled and not the *.user file. Any developer could check-out source from version control and open the Qt project ( *.pro) in Qt Creator and build.

    Thanks in advance for any tips or suggestions,

    -Ed
    Qt 5.1.0 x32
    Qt 5.1.0 x64
    Win7 x64
    VS2010
    VS2012

    1 Reply Last reply
    0
    • JKSHJ Offline
      JKSHJ Offline
      JKSH
      Moderators
      wrote on last edited by
      #2

      Not that I know of. You can submit a feature request at http://bugreports.qt-project.org/

      The .pro.user file is definitely NOT meant to be version controlled. It is a file that records settings for your local computer only -- Qt Creator will give you a warning if you load a .pro.user file that was created on another computer.

      It should take only 3 seconds to uncheck any kits that you don't want, and click the "Configure Project" button. This only needs to be done once per project per PC -- you don't have to reconfigure if you update your source code.

      Also, kits were introduced in Qt Creator 2.6, which was released in the era of Qt 4.8.3; it is not related to Qt 5.

      Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

      1 Reply Last reply
      0
      • E Offline
        E Offline
        EdOfTheMountain
        wrote on last edited by
        #3

        Thank you for your informative reply.

        I agree that it takes an experienced Qt developer familiar with a particular Qt project maybe 3 seconds to configure. For developers new to a project or developers not necessarily experienced with Qt Creator it confuses them and takes much longer than 3 seconds to learn how to configure a project.

        While I think kits are great, especially for cross platform development, I prefer the pre-kit behavior of opening a Qt project or a method of automatically selecting a default kit configuration. I may submit a feature request for something like this.

        Thanks again,
        -Ed

        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