Accessing PWD in C++ Code












0















In Qt Creator in the Projects Build Settings, you can set environment variables so that once you're done your system does not retain the env vars that were set while developing. The environment variable I have would contain the path of the developer's code. I would like to not have each developer have to input this value. I have read that there's a .pro.shared that can contain this information, however since the environment variable will point to the user's code directory and will be different for each user, it would not work for this.



What is the best way to do this?



I tried variations of the following:



MyProject.pro



DEFINES += MY_VAR=$PWD


main.cpp



#ifdef MY_VAR

qDebug() << "printing value: " << QString(MY_VAR);

#endif


Any suggestions are welcomed. The solution I'm looking for doesn't have to be a .pro file edit, as long as it is something that can be version controlled.



Not a duplicate question because...There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.






c++ qt qt-creator







share|improve this question




















  • 1





    Possible duplicate of Get current working directory in a Qt application

    – m.s.
    Jun 17 '16 at 18:14






  • 1





    So you want current directory at build time? Or runtime?

    – hyde
    Jun 17 '16 at 18:20











  • There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

    – kmx78
    Jun 17 '16 at 20:17






  • 1





    @kmx78 Paths set at build time sound like a bad time.

    – Cubic
    Jun 17 '16 at 20:20











  • I'm not trying to set a path, just trying to have access to a path.

    – kmx78
    Jun 17 '16 at 20:25
















0















In Qt Creator in the Projects Build Settings, you can set environment variables so that once you're done your system does not retain the env vars that were set while developing. The environment variable I have would contain the path of the developer's code. I would like to not have each developer have to input this value. I have read that there's a .pro.shared that can contain this information, however since the environment variable will point to the user's code directory and will be different for each user, it would not work for this.



What is the best way to do this?



I tried variations of the following:



MyProject.pro



DEFINES += MY_VAR=$PWD


main.cpp



#ifdef MY_VAR

qDebug() << "printing value: " << QString(MY_VAR);

#endif


Any suggestions are welcomed. The solution I'm looking for doesn't have to be a .pro file edit, as long as it is something that can be version controlled.



Not a duplicate question because...There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.






c++ qt qt-creator







share|improve this question




















  • 1





    Possible duplicate of Get current working directory in a Qt application

    – m.s.
    Jun 17 '16 at 18:14






  • 1





    So you want current directory at build time? Or runtime?

    – hyde
    Jun 17 '16 at 18:20











  • There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

    – kmx78
    Jun 17 '16 at 20:17






  • 1





    @kmx78 Paths set at build time sound like a bad time.

    – Cubic
    Jun 17 '16 at 20:20











  • I'm not trying to set a path, just trying to have access to a path.

    – kmx78
    Jun 17 '16 at 20:25














0












0








0








In Qt Creator in the Projects Build Settings, you can set environment variables so that once you're done your system does not retain the env vars that were set while developing. The environment variable I have would contain the path of the developer's code. I would like to not have each developer have to input this value. I have read that there's a .pro.shared that can contain this information, however since the environment variable will point to the user's code directory and will be different for each user, it would not work for this.



What is the best way to do this?



I tried variations of the following:



MyProject.pro



DEFINES += MY_VAR=$PWD


main.cpp



#ifdef MY_VAR

qDebug() << "printing value: " << QString(MY_VAR);

#endif


Any suggestions are welcomed. The solution I'm looking for doesn't have to be a .pro file edit, as long as it is something that can be version controlled.



Not a duplicate question because...There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.






c++ qt qt-creator







share|improve this question
















In Qt Creator in the Projects Build Settings, you can set environment variables so that once you're done your system does not retain the env vars that were set while developing. The environment variable I have would contain the path of the developer's code. I would like to not have each developer have to input this value. I have read that there's a .pro.shared that can contain this information, however since the environment variable will point to the user's code directory and will be different for each user, it would not work for this.



What is the best way to do this?



I tried variations of the following:



MyProject.pro



DEFINES += MY_VAR=$PWD


main.cpp



#ifdef MY_VAR

qDebug() << "printing value: " << QString(MY_VAR);

#endif


Any suggestions are welcomed. The solution I'm looking for doesn't have to be a .pro file edit, as long as it is something that can be version controlled.



Not a duplicate question because...There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.






c++ qt qt-creator




c++ qt qt-creator






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 17 '16 at 20:19







kmx78

















asked Jun 17 '16 at 18:11









kmx78kmx78

508




508








  • 1





    Possible duplicate of Get current working directory in a Qt application

    – m.s.
    Jun 17 '16 at 18:14






  • 1





    So you want current directory at build time? Or runtime?

    – hyde
    Jun 17 '16 at 18:20











  • There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

    – kmx78
    Jun 17 '16 at 20:17






  • 1





    @kmx78 Paths set at build time sound like a bad time.

    – Cubic
    Jun 17 '16 at 20:20











  • I'm not trying to set a path, just trying to have access to a path.

    – kmx78
    Jun 17 '16 at 20:25














  • 1





    Possible duplicate of Get current working directory in a Qt application

    – m.s.
    Jun 17 '16 at 18:14






  • 1





    So you want current directory at build time? Or runtime?

    – hyde
    Jun 17 '16 at 18:20











  • There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

    – kmx78
    Jun 17 '16 at 20:17






  • 1





    @kmx78 Paths set at build time sound like a bad time.

    – Cubic
    Jun 17 '16 at 20:20











  • I'm not trying to set a path, just trying to have access to a path.

    – kmx78
    Jun 17 '16 at 20:25








1




1





Possible duplicate of Get current working directory in a Qt application

– m.s.
Jun 17 '16 at 18:14





Possible duplicate of Get current working directory in a Qt application

– m.s.
Jun 17 '16 at 18:14




1




1





So you want current directory at build time? Or runtime?

– hyde
Jun 17 '16 at 18:20





So you want current directory at build time? Or runtime?

– hyde
Jun 17 '16 at 18:20













There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

– kmx78
Jun 17 '16 at 20:17





There are folders in my app's code that are relative to the application's directory. Because the end user's application and a developer's application will be in different places, I want to allow the developer to use directories that are relative to where their code resides. So I want to set the variable at build time and use it at run time.

– kmx78
Jun 17 '16 at 20:17




1




1





@kmx78 Paths set at build time sound like a bad time.

– Cubic
Jun 17 '16 at 20:20





@kmx78 Paths set at build time sound like a bad time.

– Cubic
Jun 17 '16 at 20:20













I'm not trying to set a path, just trying to have access to a path.

– kmx78
Jun 17 '16 at 20:25





I'm not trying to set a path, just trying to have access to a path.

– kmx78
Jun 17 '16 at 20:25












1 Answer
1






active

oldest

votes


















1














I just happened to have stumbled across the solution somewhere else. In case anyone else is still looking, it turns out that all I needed were 3 back slashes for quotes in my .pro file:



DEFINES += MY_VAR=\"$$PWD\"





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%2f37887833%2faccessing-pwd-in-c-code%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









    1














    I just happened to have stumbled across the solution somewhere else. In case anyone else is still looking, it turns out that all I needed were 3 back slashes for quotes in my .pro file:



    DEFINES += MY_VAR=\"$$PWD\"





    share|improve this answer




























      1














      I just happened to have stumbled across the solution somewhere else. In case anyone else is still looking, it turns out that all I needed were 3 back slashes for quotes in my .pro file:



      DEFINES += MY_VAR=\"$$PWD\"





      share|improve this answer


























        1












        1








        1







        I just happened to have stumbled across the solution somewhere else. In case anyone else is still looking, it turns out that all I needed were 3 back slashes for quotes in my .pro file:



        DEFINES += MY_VAR=\"$$PWD\"





        share|improve this answer













        I just happened to have stumbled across the solution somewhere else. In case anyone else is still looking, it turns out that all I needed were 3 back slashes for quotes in my .pro file:



        DEFINES += MY_VAR=\"$$PWD\"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 1 '17 at 22:29









        kmx78kmx78

        508




        508
































            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%2f37887833%2faccessing-pwd-in-c-code%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

            Contact image not getting when fetch all contact list from iPhone by CNContact

            Image
            up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
            Read more

            count number of partitions of a set with n elements into k subsets

            Image
            up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
            Read more

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Image
            0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
            Read more