to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. Using Conan commands, the don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method

are copied in /bin the rest of the libraries should be found in the /lib folder. But it’s just a convention, different layouts are possible. Install the requirements (from the mytimer/build folder), and that it will build “Hello” from sources. • Build and launch the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. Using conan commands, the Generating the package PROJECT: Package folder C:\Users\conan\example_conan_flow\tmp\package PROJECT: Calling package() PROJECT package(): Copied 1 '.h' files: hello.h PROJECT package(): Copied 2 '.lib' files:

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) that it will build “Hello” from sources. • Build and launch the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. Using conan commands, the don’t want to call conan create. This way you can keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging pre-built binaries If the files we want to

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method

are copied in /bin the rest of the libraries should be found in the /lib folder. But it’s just a convention, different layouts are possible. Install the requirements (from the mytimer/build folder), and that it will build “Hello” from sources. • Build and launch the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. Using conan commands, the don’t want to call conan create. This way you can keep your build cache if you are using an IDE or calling locally to the conan build command. 6.4.1 Packaging pre-built binaries If the files we want to

are copied in /bin the rest of the libraries should be found in the /lib folder. But it’s just a convention, different layouts are possible. Install the requirements (from the mytimer/build folder), and that it will build “Hello” from sources. • Build and launch the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. Using conan commands, the don’t want to call conan create. This way you can keep your build cache if you are using an IDE or calling locally to the conan build command. 6.4.1 Packaging pre-built binaries If the files we want to

to /bin. The rest of the libraries should be found in the /lib folder, however, this is just a convention, and different layouts are possible. Install the requirements (from the mytimer/build folder) it will build “Hello” from the sources. • Builds and launches the example consuming application, calling the test_package/conanfile.py build() and test() methods respectively. 34 Chapter 5. Creating Packages don’t want to call conan create. This method will keep your build cache if you are using an IDE or calling locally to the conan build command. 5.4.1 Packaging Pre-built Binaries Running the build() method