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. [SOLVED] user settings file and collaborative work
Forum Update on Monday, May 27th 2025

[SOLVED] user settings file and collaborative work

Scheduled Pinned Locked Moved Qt Creator and other tools
5 Posts 2 Posters 1.4k Views
  • 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.
  • P Offline
    P Offline
    postb99
    wrote on last edited by
    #1

    Hello,

    Reading "this old closed feature request":https://bugreports.qt-project.org/browse/QTCREATORBUG-7888 I think of basic project situation which I work with right now:

    • I develop a custom Qt plugin
    • I have to copy my dll to a specific folder for execution by a plugins host
    • I have to run a custom executable to launch this plugins host program and use my custom plugin
    • An environment variable is used for base path of commands configured in build/run settings

    So if anyone else works on project it would be fine that:

    • when reconfiguring project since his/her kit is slightly different from mine, all the other things are kept (build/run custom commands). I didn't verify what happens
    • timestamp change wouldn't be effective so often, only when there are modifications, this would be better when working with version control.

    So my suggestion is to move commands to another file than the user settings, surely in a custom syntax in .pro file. This way we could also have build/run commands way more flexible (use of environment variables, not just elimited to %sourceDir% and %buildDir%).

    And keep other things in .pro.user that would be safely ignored by version control without loosing information.

    This idea came to me immediately after playing with build/run settings, I told myself, duh this is not as convenient as in Visual Studio (where I daily practice C#).

    Just my two cents :-)

    Thanks for reading.

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      You should bring this discussion to the Qt-Creator "mailing list":http://lists.qt-project.org/mailman/listinfo/qt-creator you'll find there Qt-Creator's developers/maintainers (this forum is more user oriented)

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • P Offline
        P Offline
        postb99
        wrote on last edited by
        #3

        Thanks, just posted there. So if people are interested :-)

        1 Reply Last reply
        0
        • P Offline
          P Offline
          postb99
          wrote on last edited by
          #4

          I just got an answer, the answer is here : use .pro.shared files! Just fine...

          https://qt-project.org/doc/qtcreator-3.0/creator-sharing-project-settings.html

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            Nice !

            Since you had a working answer, please update the thread title prepending [solved] so other forum users may know that a solution has been found :)

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            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