Back to Basics: The Structure of a Program Bob Steagall CppCon 2020 K E W B C O M P U T I N GCopyright © 2020 Bob Steagall K E W B C O M P U T I N G Overview • The process of building a program • What rule (ODR) • Storage duration • ABIs and name-mangling • Linking and loading CppCon 2020 - The Structure of a Program 2Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Goals • Describe a few important CppCon 2020 - The Structure of a Program 3Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Building and Running a C++ Program • 50,000 ft view CppCon 2020 - The Structure of a Program 4 Input

Application of C++ in Cancer Modeling • The speaker (Ruibo) • University of Washington, department of applied mathematics • Cancer Modeling Group: Evolution of cancer initiation • Group leader:

by the client application. 3 Conan Documentation, Release 2.5.0 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

by the client application. 3 Conan Documentation, Release 2.1.0 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

by the client application. 3 Conan Documentation, Release 2.4.1 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

by the client application. 3 Conan Documentation, Release 2.3.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

by the client application. 3 Conan Documentation, Release 2.2.3 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

the client application. 3 Conan Documentation, Release 2.10.1 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default

by the client application. 3 Conan Documentation, Release 2.9.3 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing package_id_mode, options, transitive_headers, transitive_libs) and package types (static, shared, application, header-only) to better represent the relations that happen with C and C++ binaries, like executables it is well known that when an application myapp is linking a static library mylib, any change in the binary of the static library mylib requires re-building the application myapp. So Conan will default