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. .pro.user and version control

.pro.user and version control

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
7 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.
  • G Offline
    G Offline
    GrahamLa
    wrote on 18 Apr 2019, 10:21 last edited by
    #1

    Hi
    I am using git as my version control tool.
    I have setup shadow builds for my project and set the folders for these builds as

    D:\QtBuilds\%{CurrentProject:Name}\%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}
    

    Now I believe that this is stored in the .pro.user file and no where else.
    So if I add .pro.user to git, every time that I quit Creator this file is updated and needs to be checked into git or reverted.
    Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
    Thanks

    A 1 Reply Last reply 18 Apr 2019, 10:27
    0
    • G GrahamLa
      18 Apr 2019, 10:21

      Hi
      I am using git as my version control tool.
      I have setup shadow builds for my project and set the folders for these builds as

      D:\QtBuilds\%{CurrentProject:Name}\%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}
      

      Now I believe that this is stored in the .pro.user file and no where else.
      So if I add .pro.user to git, every time that I quit Creator this file is updated and needs to be checked into git or reverted.
      Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?
      Thanks

      A Offline
      A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on 18 Apr 2019, 10:27 last edited by aha_1980
      #2

      @GrahamLa said in .pro.user and version control:

      Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?

      Currently no, sadly.

      That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.

      To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.

      PS: The default also uses a function to remove special chars from the build directory name to avoid problems: %{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")}

      Qt has to stay free or it will die.

      G 2 Replies Last reply 18 Apr 2019, 10:44
      3
      • A aha_1980
        18 Apr 2019, 10:27

        @GrahamLa said in .pro.user and version control:

        Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?

        Currently no, sadly.

        That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.

        To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.

        PS: The default also uses a function to remove special chars from the build directory name to avoid problems: %{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")}

        G Offline
        G Offline
        GrahamLa
        wrote on 18 Apr 2019, 10:44 last edited by
        #3

        @aha_1980
        Hi
        I have set the default build directory but the output does not go to the specified folder - it now goes to debug/release in the the project folder

        A 1 Reply Last reply 18 Apr 2019, 11:04
        0
        • A aha_1980
          18 Apr 2019, 10:27

          @GrahamLa said in .pro.user and version control:

          Is there a way of setting up shadow builds such that they dont get stored in the .pro.user?

          Currently no, sadly.

          That said: Don't check in the *.pro.user into version control! It will break anytime you upgrade Qt, Creator or check out on a different machine.

          To achive what you want, it would be the easiest to set up the default build directory in Tools > Options > Build & Run > General.

          PS: The default also uses a function to remove special chars from the build directory name to avoid problems: %{JS: Util.asciify("build-%{CurrentProject:Name}-%{CurrentKit:FileSystemName}-%{CurrentBuild:Name}")}

          G Offline
          G Offline
          GrahamLa
          wrote on 18 Apr 2019, 11:03 last edited by
          #4

          @aha_1980
          It seems that the default build path is only set on project creation

          A 1 Reply Last reply 18 Apr 2019, 11:04
          0
          • G GrahamLa
            18 Apr 2019, 10:44

            @aha_1980
            Hi
            I have set the default build directory but the output does not go to the specified folder - it now goes to debug/release in the the project folder

            A Offline
            A Offline
            aha_1980
            Lifetime Qt Champion
            wrote on 18 Apr 2019, 11:04 last edited by
            #5

            @GrahamLa

            • Which build system are you using?
            • What did you enter as default build directory?
            • Did you remove the .pro.user and the build directory and open the project again?

            Qt has to stay free or it will die.

            1 Reply Last reply
            0
            • G GrahamLa
              18 Apr 2019, 11:03

              @aha_1980
              It seems that the default build path is only set on project creation

              A Offline
              A Offline
              aha_1980
              Lifetime Qt Champion
              wrote on 18 Apr 2019, 11:04 last edited by
              #6

              @GrahamLa said in .pro.user and version control:

              @aha_1980
              It seems that the default build path is only set on project creation

              Yes, that's how it works.

              Qt has to stay free or it will die.

              G 1 Reply Last reply 18 Apr 2019, 11:55
              0
              • A aha_1980
                18 Apr 2019, 11:04

                @GrahamLa said in .pro.user and version control:

                @aha_1980
                It seems that the default build path is only set on project creation

                Yes, that's how it works.

                G Offline
                G Offline
                GrahamLa
                wrote on 18 Apr 2019, 11:55 last edited by
                #7

                @aha_1980
                OK thanks - I'll sort something from here

                1 Reply Last reply
                0

                7/7

                18 Apr 2019, 11:55

                • Login

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