#include // [...]10/50 Hello Modules! — File: module.cpp export module my_module; export char const* my_function () { return "Hello Modules!"; } — File: main.cpp #include }11/50 Exporting things // functions export int getNumber (); // types export class SomeType; // templates export template T combine(T n1 , T n2); export template class MyTemplatedType Exporting things export namespace a { void is_exported (); } namespace a { void is_not_exported (); } namespace a { void will_be_exported_in_b (); } export namespace b { export using a:: will_be_exported_in_b

object file 6 . 2 discarded discarded some header.hsource.cpp translation unit object file export module library; library interface unit module library; library implementation library implementation implementation object file import library; program library interface object file 7 . 1 export ...; export ...; BMI BMI Barrier→║ Architected→→ modularized library some allinterface.cpp declarations 4 5 6 7 8 9 module; #include export module my.first_module; export import other.module; #include "mod.h" constexpr int beast = 666; export std::vector frob(S); 1 2 3 4 5 6 7 8 9

attribute won’t exist in Conan 2.0. You have to start using the export() and source() methods to mimic the same behavior: • The export() method is responsible for capturing the “coordinates” of the current new conan.tools.scm.Git can be used for this (do not use the legacy Git helper but this one) • The export() method, after capturing the coordinates, can store them in the conandata.yml using the update_conandata() tools.scm import Git from conan.tools.files import load, update_conandata class Pkg(Conanfile): def export(self): git = Git(self, self.recipe_folder) scm_url, scm_commit = git.get_url_and_commit() update_conandata(self

attribute won’t exist in Conan 2.0. You have to start using the export() and source() methods to mimic the same behavior: • The export() method is responsible for capturing the “coordinates” of the current new conan.tools.scm.Git can be used for this (do not use the legacy Git helper but this one) • The export() method, after capturing the coordinates, can store them in the conandata.yml using the update_conandata() tools.scm import Git from conan.tools.files import load, update_conandata class Pkg(Conanfile): def export(self): git = Git(self, self.recipe_folder) scm_url, scm_commit = git.get_url_and_commit() update_conandata(self

attribute won’t exist in Conan 2.0. You have to start using the export() and source() methods to mimic the same behavior: • The export() method is responsible for capturing the “coordinates” of the current new conan.tools.scm.Git can be used for this (do not use the legacy Git helper but this one) • The export() method, after capturing the coordinates, can store them in the conandata.yml using the update_conandata() tools.scm import Git from conan.tools.files import load, update_conandata class Pkg(Conanfile): def export(self): git = Git(self, self.recipe_folder) scm_url, scm_commit = git.get_url_and_commit() update_conandata(self

attribute won’t exist in Conan 2.0. You have to start using the export() and source() methods to mimic the same behavior: • The export() method is responsible for capturing the “coordinates” of the current new conan.tools.scm.Git can be used for this (do not use the legacy Git helper but this one) • The export() method, after capturing the coordinates, can store them in the conandata.yml using the update_conandata() tools.scm import Git from conan.tools.files import load, update_conandata class Pkg(Conanfile): def export(self): git = Git(self, self.recipe_folder) scm_url, scm_commit = git.get_url_and_commit() update_conandata(self

world Release!” is displayed, it worked. The conan create command does the following: • Copies (“export” in Conan terms) the conanfile.py from the user folder into the local cache. • Installs the package Release 1.26.1 Using Conan commands, the conan create command would be equivalent to: $ conan export . demo/testing $ conan install hello/0.1@demo/testing --build=hello # package is created now, use There are two different approaches: • Using the exports sources attribute of the conanfile to export the source code together with the recipe. This way the recipe is self-contained and will not need

attribute won’t exist in Conan 2.0. You have to start using the export() and source() methods to mimic the same behavior: • The export() method is responsible for capturing the “coordinates” of the current new conan.tools.scm.Git can be used for this (do not use the legacy Git helper but this one) • The export() method, after capturing the coordinates, can store them in the conandata.yml using the update_conandata() migration guide to 2.0 Conan Documentation, Release 1.52.0 (continued from previous page) def export(self): git = Git(self, self.recipe_folder) scm_url, scm_commit = git.get_url_and_commit() update_conandata(self

world Release!” is displayed, it worked. The conan create command does the following: • Copies (“export” in Conan terms) the conanfile.py from the user folder into the local cache. • Installs the package Release 1.31.4 Using Conan commands, the conan create command would be equivalent to: $ conan export . demo/testing $ conan install hello/0.1@demo/testing --build=hello # package is created now, use There are two different approaches: • Using the exports sources attribute of the conanfile to export the source code together with the recipe. This way the recipe is self-contained and will not need

world Release!” is displayed, it worked. The conan create command does the following: • Copies (“export” in Conan terms) the conanfile.py from the user folder into the local cache. • Installs the package Release 1.30.2 Using Conan commands, the conan create command would be equivalent to: $ conan export . demo/testing $ conan install hello/0.1@demo/testing --build=hello # package is created now, use There are two different approaches: • Using the exports sources attribute of the conanfile to export the source code together with the recipe. This way the recipe is self-contained and will not need