command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 5.3. Workflows 31 Conan Documentation, Release 1.36.0 5.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 5.3. Workflows 31 Conan Documentation, Release 1.35.2 5.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 5.3. Workflows 31 Conan Documentation, Release 1.34.1 5.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 6.3. Workflows 45 Conan Documentation, Release 1.39.0 6.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 6.3. Workflows 45 Conan Documentation, Release 1.40.4 6.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 6.3. Workflows 45 Conan Documentation, Release 1.41.0 6.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 5.3. Workflows 31 Conan Documentation, Release 1.30.2 5.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 5.3. Workflows 31 Conan Documentation, Release 1.31.4 5.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 6.3. Workflows 45 Conan Documentation, Release 1.38.0 6.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say

command line. The applied configuration will be the composition of all the profiles applied in the order they are specified: $ conan install .. -pr=../poco_clang_3.5 -pr=my_build_tool1 -pr=my_build_tool2 sual_studio_multi 6.3. Workflows 45 Conan Documentation, Release 1.37.2 6.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find the source files building with gcc 4.9. We can define an ordered list of compatible packages, that will be checked in order if the package ID that our profile defines is not available. Let’s see it with an example: Lets say