configurations, in-source or out of source, and you can switch between them without taking the extra step of re-issuing the conan install command (even though this is not a speed-related issue, since the second You will generally want to start off with the conan source command. The strategy here is that you’re testing your source method in isolation, and downloading the files to a temporary sub-folder relative txt Hello/0.1@user/channel (test package): Running build() ... There is often a need to repeatedly re-run the test to check the package is well generated for consumers. As a summary, you could use the

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again a new binary for it. Exactly the same for patches, changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: 5.6. Defining Package ABI

configurations, in-source or out of source, and you can switch between them without taking the extra step of re-issuing the conan install command (even though this is not a speed-related issue, since the second a new binary for it. Exactly the same for patches, changing from 2.1.10 to 2.1.11 doesn’t require a re-build. Those rules are defined by semver. If it is necessary to change the default behavior, the applied implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this case, it could make sense: def package_id(self): # Any change in the MyOtherLib

configurations, in-source or out of source, and you can switch between them without taking the extra step of re-issuing the conan install command (even though this is not a speed-related issue, since the second a new binary for it. Exactly the same for patches, changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from MyLib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: 5.6. Defining Package ABI

different configurations, whether in-source or out of source, and switch between them without having to re-issue the conan install command (Note however, that even if you did have to run conan install again binary for it. This also applies to patches, whereby changing from 2.1.10 to 2.1.11 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized implementation of some functions that will be inlined when compiled from my_lib/1.0 will definitely require re-building. For this case, it could make sense to have this configuration: def package_id(self): #