dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for

dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for

disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. 276 Chapter 14. Reference conan Documentation, Release recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for unpredictable results. The most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. description This is an optional, but strongly recommended

disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for unpredictable results. The most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. 280 Chapter 14. Reference conan Documentation, Release

disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for unpredictable results. The most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. 284 Chapter 14. Reference conan Documentation, Release

disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. 292 Chapter 14. Reference conan Documentation, Release recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for unpredictable results. The most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. description This is an optional, but strongly recommended

dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for

dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for

dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for

dynamically define the name and version of a package The name and version fields are used to define constant values. The set_name() and set_version() methods can be used to dynamically define those values disk). However, the most common and suggested approach would be to define it in plain text as a constant, or provide it as command line arguments. version The version attribute will define the version recipe in other places (as in source() method to retrieve code from elsewhere), making this value not constant means that it may evaluate differently in different contexts (e.g., on different machines or for