Visual Studio pro 2017 build dependency problem












1














I have a Visual Studio C++ solution that seems to have a dependency problem somehow. Here is some info:




  1. It always builds correctly in Debug mode

  2. It always builds correctly in Release mode IF I do a "Clean Solution" first

  3. It builds incorrectly in Release mode otherwise. If I update a value in a header file, the compiled result will still have the old value.


Here is more information. The parameter that I change is a single value in my file release.h. This file has one line where I #define VERSION. VERSION is used in a function that returns the current version of my software. When I build after changing this value in the header file, the system correctly recognizes that the source file must be recompiled. After it recompiles the source file, I get the following:



1> Generating code
1> 0 of 168 functions ( 0.0%) were compiled, the rest were copied from previous compilation.
1> 0 functions were new in current compilation
1> 0 functions had inline decision re-evaluated but remain unchanged


I also verified that the same behavior happens if I replace the VERSION macro and use the number directly. If I only change the number, I get the same result as far as having to do a do a "Clean Solution" for the solution to build correctly.



Lastly, if I add a line of dummy code to the function such as:



int i = 7;  // i is not used in the function


the build will work correctly the next time. In this case, after the source file is recompiled, we see the following:



1> Generating code
1> 2 of 168 functions ( 1.2%) were compiled, the rest were copied from previous compilation.
1> 0 functions were new in current compilation
1> 0 functions had inline decision re-evaluated but remain unchanged


Further compiles will not work correctly unless something changes like removing
the int i = 7;



in which case, it will work the next time.



Thoughts?










share|improve this question





























    1














    I have a Visual Studio C++ solution that seems to have a dependency problem somehow. Here is some info:




    1. It always builds correctly in Debug mode

    2. It always builds correctly in Release mode IF I do a "Clean Solution" first

    3. It builds incorrectly in Release mode otherwise. If I update a value in a header file, the compiled result will still have the old value.


    Here is more information. The parameter that I change is a single value in my file release.h. This file has one line where I #define VERSION. VERSION is used in a function that returns the current version of my software. When I build after changing this value in the header file, the system correctly recognizes that the source file must be recompiled. After it recompiles the source file, I get the following:



    1> Generating code
    1> 0 of 168 functions ( 0.0%) were compiled, the rest were copied from previous compilation.
    1> 0 functions were new in current compilation
    1> 0 functions had inline decision re-evaluated but remain unchanged


    I also verified that the same behavior happens if I replace the VERSION macro and use the number directly. If I only change the number, I get the same result as far as having to do a do a "Clean Solution" for the solution to build correctly.



    Lastly, if I add a line of dummy code to the function such as:



    int i = 7;  // i is not used in the function


    the build will work correctly the next time. In this case, after the source file is recompiled, we see the following:



    1> Generating code
    1> 2 of 168 functions ( 1.2%) were compiled, the rest were copied from previous compilation.
    1> 0 functions were new in current compilation
    1> 0 functions had inline decision re-evaluated but remain unchanged


    Further compiles will not work correctly unless something changes like removing
    the int i = 7;



    in which case, it will work the next time.



    Thoughts?










    share|improve this question



























      1












      1








      1







      I have a Visual Studio C++ solution that seems to have a dependency problem somehow. Here is some info:




      1. It always builds correctly in Debug mode

      2. It always builds correctly in Release mode IF I do a "Clean Solution" first

      3. It builds incorrectly in Release mode otherwise. If I update a value in a header file, the compiled result will still have the old value.


      Here is more information. The parameter that I change is a single value in my file release.h. This file has one line where I #define VERSION. VERSION is used in a function that returns the current version of my software. When I build after changing this value in the header file, the system correctly recognizes that the source file must be recompiled. After it recompiles the source file, I get the following:



      1> Generating code
      1> 0 of 168 functions ( 0.0%) were compiled, the rest were copied from previous compilation.
      1> 0 functions were new in current compilation
      1> 0 functions had inline decision re-evaluated but remain unchanged


      I also verified that the same behavior happens if I replace the VERSION macro and use the number directly. If I only change the number, I get the same result as far as having to do a do a "Clean Solution" for the solution to build correctly.



      Lastly, if I add a line of dummy code to the function such as:



      int i = 7;  // i is not used in the function


      the build will work correctly the next time. In this case, after the source file is recompiled, we see the following:



      1> Generating code
      1> 2 of 168 functions ( 1.2%) were compiled, the rest were copied from previous compilation.
      1> 0 functions were new in current compilation
      1> 0 functions had inline decision re-evaluated but remain unchanged


      Further compiles will not work correctly unless something changes like removing
      the int i = 7;



      in which case, it will work the next time.



      Thoughts?










      share|improve this question















      I have a Visual Studio C++ solution that seems to have a dependency problem somehow. Here is some info:




      1. It always builds correctly in Debug mode

      2. It always builds correctly in Release mode IF I do a "Clean Solution" first

      3. It builds incorrectly in Release mode otherwise. If I update a value in a header file, the compiled result will still have the old value.


      Here is more information. The parameter that I change is a single value in my file release.h. This file has one line where I #define VERSION. VERSION is used in a function that returns the current version of my software. When I build after changing this value in the header file, the system correctly recognizes that the source file must be recompiled. After it recompiles the source file, I get the following:



      1> Generating code
      1> 0 of 168 functions ( 0.0%) were compiled, the rest were copied from previous compilation.
      1> 0 functions were new in current compilation
      1> 0 functions had inline decision re-evaluated but remain unchanged


      I also verified that the same behavior happens if I replace the VERSION macro and use the number directly. If I only change the number, I get the same result as far as having to do a do a "Clean Solution" for the solution to build correctly.



      Lastly, if I add a line of dummy code to the function such as:



      int i = 7;  // i is not used in the function


      the build will work correctly the next time. In this case, after the source file is recompiled, we see the following:



      1> Generating code
      1> 2 of 168 functions ( 1.2%) were compiled, the rest were copied from previous compilation.
      1> 0 functions were new in current compilation
      1> 0 functions had inline decision re-evaluated but remain unchanged


      Further compiles will not work correctly unless something changes like removing
      the int i = 7;



      in which case, it will work the next time.



      Thoughts?







      visual-studio build dependencies






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 at 5:01









      Wai Ha Lee

      5,743123663




      5,743123663










      asked Nov 20 at 4:57









      Dave M

      63




      63





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53386480%2fvisual-studio-pro-2017-build-dependency-problem%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53386480%2fvisual-studio-pro-2017-build-dependency-problem%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Paul Cézanne

          UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

          Angular material date-picker (MatDatepicker) auto completes the date on focus out