${configurationName} variable - support #1444

Activity

1. sean-mcmanus commented on Jan 16, 2018

   

   Sean McManus (sean-mcmanus)

   on Jan 16, 2018

   Contributor

   More actions

   I don't think extensions have a way of adding task variables, so someone would need to get VS Code to add this ability. You may be able to work around this by using an environment variables of the form ${env:configurationName} and then somehow changing the value of the environment variable when a configuration changes, such as via adding code in onSelectedConfigurationChanged in https://github.com/Microsoft/vscode-cpptools/blob/master/Extension/src/LanguageServer/client.ts , but if we want this change to be shipped in the product, it seems like the name of the environment variable would need to be a setting so that it's customizable.
2. Sean McManus (sean-mcmanus)

   added

   Feature Request

   help wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.

   on Jan 16, 2018
3. sean-mcmanus commented on Jan 26, 2018

   

   Sean McManus (sean-mcmanus)

   on Jan 26, 2018

   Contributor

   More actions

   This can be implemented in our open source code via adding a C_Cpp.configuration setting and the using ${config.C_Cpp.configuration} in your task.json. The config index is currently saved in the workspace "persistent state". I agree it would be good to add, but I'm not sure when we'll get around to it yet due to higher priority tasks.
4. witM commented on Jan 26, 2018

   

   infomaks (witM)

   on Jan 26, 2018 via email

   Author

   More actions

   Thanks for informations, I'll be look for future updates for this. It seems to be natural to be something like this variable. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

   …

   On Fri, Jan 26, 2018 at 2:16 AM, Sean McManus ***@***.***> wrote: This can be implemented in our open source code via adding a C_Cpp.configuration setting and the using ${config.C_Cpp.configuration} in your task.json. The config index is currently saved in the workspace "persistent state". I agree it would be good to add, but I'm not sure when we'll get around to it yet due to higher priority tasks. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1444 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKwVo0Cno36ZTqNn3WGGn7jqHX0OnljZks5tOSd4gaJpZM4RdKuN> .
5. Michelle Matias (michelleangela)

   added this to the Backlog milestone on Jun 12, 2019
6. bobbrow commented on Sep 9, 2019

   

   Bob Brown (bobbrow)

   on Sep 9, 2019

   Contributor

   More actions

   You can use ${command:cpptools.activeConfigName} to get the value of the active configuration. Is that what you were asking for?
7. Bob Brown (bobbrow)

   closed this as completedon Sep 9, 2019
8. github-actions

   locked and limited conversation to collaborators on Oct 15, 2020