4/7/2024 0 Comments Clion run configuration![]() So whenever you run/debug or test your code, CLion either uses an existing permanent run/debug configuration or creates a new temporary one. Permanent configurations remain as part of your project until you remove them. Permanent - created explicitly from a template or by saving a temporary configuration. If necessary, you can increase this limit in Settings/Preferences | Advanced Settings | IDE | Temporary Run/Debug configurations limit. The older ones are automatically deleted when new ones are added. The maximum number of temporary configurations is 5. Temporary - created every time you run/debug a test, test suite, fixture, or a main() entry use the gutter icons /.Run/debug configurations can be created as: If the Navigation bar is visible ( View | Appearance | Navigation Bar), you can access all available run/debug configurations from the selector on the toolbar. However, you can edit default values of parameters in each template to streamline the creation of new configurations. ![]() The list of available templates is predefined in the installation and can only be extended via plugins. When you create a new configuration for a specific kind of executable context, you create it from one of the dedicated configuration templates, which implement the startup logic, define the list of parameters and their default values. Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used. CLion uses run/debug configurations to run, debug, and test your code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |