. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4 Debugging packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 cmake_multi and vi- sual_studio_multi 4.3. Workflows 29 Conan Documentation, Release 1.26.1 4.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find install time. They generate files, not command line arguments, providing better re- producibility and debugging of builds. • They provide a better developer experience. The command line used by developers locally

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4 Debugging packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 cmake_multi and vi- sual_studio_multi 4.3. Workflows 29 Conan Documentation, Release 1.22.3 4.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4 Debugging packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 cmake_multi and vi- sual_studio_multi 4.3. Workflows 29 Conan Documentation, Release 1.23.0 4.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4 Debugging packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 cmake_multi and vi- sual_studio_multi 4.3. Workflows 29 Conan Documentation, Release 1.24.1 4.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4 Debugging packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 cmake_multi and vi- sual_studio_multi 4.3. Workflows 29 Conan Documentation, Release 1.25.2 4.4 Debugging packages In order to run a debug session and step into the source code, the debugger needs to find that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further

locally developing packages, at some poing you might need to step-into dependencies code while debugging. Please read this example how to debug and step-into dependencies for more information about this • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like heavy .pdb files • Coverage, sanitizers, or other source or binary analysis tools some build logs need to be recovered for compliance, or some test executables might be needed for debugging or re-checking a crash. • Conan does not do any compression or decompression of the metadata files

locally developing packages, at some poing you might need to step-into dependencies code while debugging. Please read this example how to debug and step-into dependencies for more information about this • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like heavy .pdb files • Coverage, sanitizers, or other source or binary analysis tools some build logs need to be recovered for compliance, or some test executables might be needed for debugging or re-checking a crash. • Conan does not do any compression or decompression of the metadata files

locally developing packages, at some poing you might need to step-into dependencies code while debugging. Please read this example how to debug and step-into dependencies for more information about this • Full build logs • The tests executables • The tests results from running the test suite • Debugging artifacts like heavy .pdb files • Coverage, sanitizers, or other source or binary analysis tools some build logs need to be recovered for compliance, or some test executables might be needed for debugging or re-checking a crash. • Conan does not do any compression or decompression of the metadata files

that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further not intended to be defined explictly in conanfiles, altough they can for specific purposes like debugging. Read more about Package Revisions 108 Chapter 9. Versioning Conan Documentation, Release 1.19 Execute locally the conanfile.py package() method. These commands are mostly used for testing and debugging while developing a new package, before exporting such package recipe into the local cache. See

that you can open, select the app executable as StartUp project, and start building, executing, debugging, switching from Debug and Release configurations freely from the IDE, without needing to issue further not intended to be defined explictly in conanfiles, altough they can for specific purposes like debugging. Read more about Package Revisions 108 Chapter 9. Versioning Conan Documentation, Release 1.20 Execute locally the conanfile.py package() method. These commands are mostly used for testing and debugging while developing a new package, before exporting such package recipe into the local cache. See