CMake: Set Visual Studio project properties to inherit from parent (property sheet)

Multi tool use
Multi tool use












0















I'm using CMake 3.8.1 to generate Visual Studio 2015 Projects.



Adding a custom property sheet:



set_target_properties(${TARGET} PROPERTIES VS_USER_PROPS "my_settings.props")


Can't find the way in CMakeLists.txt to set "Output Directory", "Intermediate Directory" and some other Visual Studio project properties in vcxproj file to desired values. Those Output/Intermediate directories set to some default value by CMake.



Ideally I'm looking to set those properties to



<inherit from parent or project defaults>


So the project will pick up values that I have in my_settings.props



In vcsproj files, if you skip the entry for a property, it will inherit the value from parent.



Is there a way to customize/set/control those values from CMakeLists.txt file?










share|improve this question





























    0















    I'm using CMake 3.8.1 to generate Visual Studio 2015 Projects.



    Adding a custom property sheet:



    set_target_properties(${TARGET} PROPERTIES VS_USER_PROPS "my_settings.props")


    Can't find the way in CMakeLists.txt to set "Output Directory", "Intermediate Directory" and some other Visual Studio project properties in vcxproj file to desired values. Those Output/Intermediate directories set to some default value by CMake.



    Ideally I'm looking to set those properties to



    <inherit from parent or project defaults>


    So the project will pick up values that I have in my_settings.props



    In vcsproj files, if you skip the entry for a property, it will inherit the value from parent.



    Is there a way to customize/set/control those values from CMakeLists.txt file?










    share|improve this question



























      0












      0








      0








      I'm using CMake 3.8.1 to generate Visual Studio 2015 Projects.



      Adding a custom property sheet:



      set_target_properties(${TARGET} PROPERTIES VS_USER_PROPS "my_settings.props")


      Can't find the way in CMakeLists.txt to set "Output Directory", "Intermediate Directory" and some other Visual Studio project properties in vcxproj file to desired values. Those Output/Intermediate directories set to some default value by CMake.



      Ideally I'm looking to set those properties to



      <inherit from parent or project defaults>


      So the project will pick up values that I have in my_settings.props



      In vcsproj files, if you skip the entry for a property, it will inherit the value from parent.



      Is there a way to customize/set/control those values from CMakeLists.txt file?










      share|improve this question
















      I'm using CMake 3.8.1 to generate Visual Studio 2015 Projects.



      Adding a custom property sheet:



      set_target_properties(${TARGET} PROPERTIES VS_USER_PROPS "my_settings.props")


      Can't find the way in CMakeLists.txt to set "Output Directory", "Intermediate Directory" and some other Visual Studio project properties in vcxproj file to desired values. Those Output/Intermediate directories set to some default value by CMake.



      Ideally I'm looking to set those properties to



      <inherit from parent or project defaults>


      So the project will pick up values that I have in my_settings.props



      In vcsproj files, if you skip the entry for a property, it will inherit the value from parent.



      Is there a way to customize/set/control those values from CMakeLists.txt file?







      visual-studio visual-studio-2015 cmake cmake-language






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 28 '18 at 21:54







      sny

















      asked Dec 28 '18 at 21:43









      snysny

      17515




      17515
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Some (most?) of the property fields in a Visual Studio project are controlled by values set in CMakeLists.txt but there isn't a command that just sets them to what you want.



          There are many properties and variables that control how a target is built. Then each type of generator outputs a project file in accordance to those items. That's how a generator for Visual Studio builds the same artifacts as for MSYS Makefiles. Here are a few examples (that I remember):





          1. Output Directory - Refer to RUNTIME_OUTPUT_DIRECTORY


          2. Intermediate Directory - Controlled by CMake cannot change


          3. Target Name - Refer to OUTPUT_NAME


          4. Target Extension - Refer to SUFFIX


          I guess you can abuse some of these items by making them be equal to a Visual Studio variable or something but that isn't something I've ever run across.






          share|improve this answer























            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%2f53964579%2fcmake-set-visual-studio-project-properties-to-inherit-from-parent-property-she%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Some (most?) of the property fields in a Visual Studio project are controlled by values set in CMakeLists.txt but there isn't a command that just sets them to what you want.



            There are many properties and variables that control how a target is built. Then each type of generator outputs a project file in accordance to those items. That's how a generator for Visual Studio builds the same artifacts as for MSYS Makefiles. Here are a few examples (that I remember):





            1. Output Directory - Refer to RUNTIME_OUTPUT_DIRECTORY


            2. Intermediate Directory - Controlled by CMake cannot change


            3. Target Name - Refer to OUTPUT_NAME


            4. Target Extension - Refer to SUFFIX


            I guess you can abuse some of these items by making them be equal to a Visual Studio variable or something but that isn't something I've ever run across.






            share|improve this answer




























              0














              Some (most?) of the property fields in a Visual Studio project are controlled by values set in CMakeLists.txt but there isn't a command that just sets them to what you want.



              There are many properties and variables that control how a target is built. Then each type of generator outputs a project file in accordance to those items. That's how a generator for Visual Studio builds the same artifacts as for MSYS Makefiles. Here are a few examples (that I remember):





              1. Output Directory - Refer to RUNTIME_OUTPUT_DIRECTORY


              2. Intermediate Directory - Controlled by CMake cannot change


              3. Target Name - Refer to OUTPUT_NAME


              4. Target Extension - Refer to SUFFIX


              I guess you can abuse some of these items by making them be equal to a Visual Studio variable or something but that isn't something I've ever run across.






              share|improve this answer


























                0












                0








                0







                Some (most?) of the property fields in a Visual Studio project are controlled by values set in CMakeLists.txt but there isn't a command that just sets them to what you want.



                There are many properties and variables that control how a target is built. Then each type of generator outputs a project file in accordance to those items. That's how a generator for Visual Studio builds the same artifacts as for MSYS Makefiles. Here are a few examples (that I remember):





                1. Output Directory - Refer to RUNTIME_OUTPUT_DIRECTORY


                2. Intermediate Directory - Controlled by CMake cannot change


                3. Target Name - Refer to OUTPUT_NAME


                4. Target Extension - Refer to SUFFIX


                I guess you can abuse some of these items by making them be equal to a Visual Studio variable or something but that isn't something I've ever run across.






                share|improve this answer













                Some (most?) of the property fields in a Visual Studio project are controlled by values set in CMakeLists.txt but there isn't a command that just sets them to what you want.



                There are many properties and variables that control how a target is built. Then each type of generator outputs a project file in accordance to those items. That's how a generator for Visual Studio builds the same artifacts as for MSYS Makefiles. Here are a few examples (that I remember):





                1. Output Directory - Refer to RUNTIME_OUTPUT_DIRECTORY


                2. Intermediate Directory - Controlled by CMake cannot change


                3. Target Name - Refer to OUTPUT_NAME


                4. Target Extension - Refer to SUFFIX


                I guess you can abuse some of these items by making them be equal to a Visual Studio variable or something but that isn't something I've ever run across.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 29 '18 at 2:36









                FredFred

                1,28698




                1,28698






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53964579%2fcmake-set-visual-studio-project-properties-to-inherit-from-parent-property-she%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







                    h,JbRZct,QtGe1lvo1G JNprk8,8xWiQEYm6ZkdeU7t4d 0T,5tq,CIL,75j
                    H0QxMdbH tLYyiI9rR0WrkIW 6l,TDDaSR1IiHG4uyF e,dZhY1F8NjZ,nrx,lSfy2EQfw4ynFUJI95boK0L1Q,iRp,FMhuWGRr

                    Popular posts from this blog

                    Monofisismo

                    Angular Downloading a file using contenturl with Basic Authentication

                    Olmecas