@@@ All of library code is in LibSpace, user code without frame is in UserSpace@@@ As opposed to library sharing entities with other libraries+ @@@ Deducing this removes the need for CRTP2 Slides1. https://godbolt default implementation (something which can be done generally) @@@ All of library code is in LibSpace, user code without frame is in UserSpace1. @@@ Terms: 1. Overload: multiple functions with the same name library code is in LibSpace, user code without frame is in UserSpace 1. Basic: https://godbolt.org/z/nej3977z8@@@ This is done in the lib containing namespace (and not on user space) 2. Partial template

Analysis pre-recorded? | real-time? log files? | command-line tool? | GUI?, … An interactive, responsive and visual tool transforms the profiling experience! 11 Closing the Profiling Zoo holistic issues: information overload; sampling overhead; constrained by sampling frequency An interactive, responsive and visual tool transforms the profiling experience! Tracy can do it all!Tracy Profiler GUI compilation sorting, searching, container manipulations, … file, network, logging, … interrupts, user input activity, spurious wake-ups, … 46 Instrument the “usual suspects ” Tips & Tricks• Idling

Analysis pre-recorded? | real-time? log files? | command-line tool? | GUI?, … An interactive, responsive and visual tool transforms the profiling experience! 11 Closing the Profiling Zoo holistic issues: information overload; sampling overhead; constrained by sampling frequency An interactive, responsive and visual tool transforms the profiling experience!Tracy Profiler GUI 13Tracy Profiler GUI compilation sorting, searching, container manipulations, … file, network, logging, … interrupts, user input activity, spurious wake-ups, … 46 Instrument the “usual suspects ” Tips & Tricks• Idling

$ conan create . user/channel $ conan create . Pkg/0.1@user/channel $ conan create mypkgconanfile.py Pkg/0.1@user/channel $ conan export . user/channel $ conan export . Pkg/0.1@user/channel $ conan export export myfolder/myconanfile.py Pkg/0.1@user/channel This behavior aligns with the conan source, conan build, conan package commands, that all use the same argu- ments to locate the conanfile.py containing Use self.source_folder, self.build_folder, etc. in- stead • self.cpp_info, self.env_info and self.user_info scope has been reduced to only the package_info() method • gcc and ConfigureEnvironment were

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. 7 conan Documentation, Release 1.7.4 • If you are using Windows and Python <3

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. 7 conan Documentation, Release 1.6.1 • If you are using Windows and Python <3

$ conan create . user/channel $ conan create . Pkg/0.1@user/channel $ conan create mypkgconanfile.py Pkg/0.1@user/channel $ conan export . user/channel $ conan export . Pkg/0.1@user/channel $ conan export export myfolder/myconanfile.py Pkg/0.1@user/channel This behavior aligns with the conan source, conan build, conan package commands, that all use the same argu- ments to locate the conanfile.py file containing Instead, use self.source_folder, self.build_folder, etc. • self.cpp_info, self.env_info and self.user_info scope are now only included the package_info() method • gcc and ConfigureEnvironment were removed

$ conan create . user/channel $ conan create . Pkg/0.1@user/channel $ conan create mypkgconanfile.py Pkg/0.1@user/channel $ conan export . user/channel $ conan export . Pkg/0.1@user/channel $ conan export export myfolder/myconanfile.py Pkg/0.1@user/channel This behavior aligns with the conan source, conan build, conan package commands, that all use the same argu- ments to locate the conanfile.py containing Use self.source_folder, self.build_folder, etc. in- stead • self.cpp_info, self.env_info and self.user_info scope has been reduced to only the package_info() method • gcc and ConfigureEnvironment were

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. 7 conan Documentation, Release 1.9.2 • If you are using Windows and Python <3

can manage pre-compiled binaries for packages. To define a package, referenced by its name, version, user and channel, a package recipe is needed. Such a package recipe is a conanfile.py python script that build your project. 1.5 Stable From Conan 1.0, there is a commitment to stability, not breaking user space while evolving the tool and the platform. This means: • Moving forward to following minor versions System Integrity Protection, pip may fail. Try using virtualenvs, or install with another user $ pip install --user conan. 7 conan Documentation, Release 1.8.4 • If you are using Windows and Python <3