Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Qt VS Tools Always building stuff for Release build

Qt VS Tools Always building stuff for Release build

Scheduled Pinned Locked Moved Solved General and Desktop
5 Posts 3 Posters 670 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.
  • PerdrixP Online
    PerdrixP Online
    Perdrix
    wrote on last edited by Perdrix
    #1

    Scenario

    1. Select release build
    2. Run build to completion
    3. Select Debug/Start Debugging or Debug/Start Without Debugging

    Before running the executable VS Tools (or MSBuild) does a rebuild of the translation files

    Even though the project has already built to completion including the above stuff.

    I've checked the vcxproj file by hand for differences between the Debug|x64 and Release|x64 sections.

    The only difference is that I have a post build event that runs lrelease twice in the Release builds, once to put the Qt dependencies into the build directory and once to place them into the Installers\RunTIme64 directory.:

    call $(QTDIR)\bin\qtenv2.bat
    
    $(QTDIR)\bin\windeployqt $(TargetPath)
    $(QTDIR)\bin\windeployqt --dir $(SolutionDir)Installers\RunTime64 $(TargetPath)
    

    Looking around the directory tree the only other difference I found is that the qtvars...props file locations are inconsistent:

    D:\Users\amonra\Documents\GitHub\DSS>dir qtvars*.props /s
     Volume in drive D is Data
     Volume Serial Number is 2892-0083
    
     Directory of D:\Users\amonra\Documents\GitHub\DSS\DeepSkyStacker\Debug\qmake
    
    04/05/2020  03:34             1,655 qtvars_Win32_Debug.props
                   1 File(s)          1,655 bytes
    
     Directory of D:\Users\amonra\Documents\GitHub\DSS\DeepSkyStacker\Release\qmake
    
    04/05/2020  03:34             1,672 qtvars_Win32_Release.props
                   1 File(s)          1,672 bytes
    
     Directory of D:\Users\amonra\Documents\GitHub\DSS\DeepSkyStacker\x64\Debug\qmake
    
    08/06/2020  11:26             3,976 qtvars_x64_Debug.props
                   1 File(s)          3,976 bytes
    
     Directory of D:\Users\amonra\Documents\GitHub\DSS\DeepSkyStacker\x64\Release\qmake
    
    08/06/2020  16:39             3,993 qtvars_x64_Release.props
                   1 File(s)          3,993 bytes
    
    1 Reply Last reply
    0
    • PerdrixP Perdrix

      Problem solved Self inflicted problem with custom build step

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #5

      @Perdrix Please mark thread as solved

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • VRoninV Offline
        VRoninV Offline
        VRonin
        wrote on last edited by
        #2

        windeployqt doesn't have a concept of "changes", it is just run everytime

        "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
        ~Napoleon Bonaparte

        On a crusade to banish setIndexWidget() from the holy land of Qt

        1 Reply Last reply
        1
        • PerdrixP Online
          PerdrixP Online
          Perdrix
          wrote on last edited by Perdrix
          #3

          That's not the problem. It is run as part of the build for the debug build, but not every time I invoke the executable, but for the release build, every time I attempt to run the executable it re-runs all the stuff you see above - that isn't right. I removed the post build step for windeployqt and that didn't change the behaviour.

          This is driving me nuts
          David

          1 Reply Last reply
          0
          • PerdrixP Online
            PerdrixP Online
            Perdrix
            wrote on last edited by
            #4

            Problem solved Self inflicted problem with custom build step

            jsulmJ 1 Reply Last reply
            0
            • PerdrixP Perdrix

              Problem solved Self inflicted problem with custom build step

              jsulmJ Offline
              jsulmJ Offline
              jsulm
              Lifetime Qt Champion
              wrote on last edited by
              #5

              @Perdrix Please mark thread as solved

              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