diff --git a/md__2____w_2rippled_2rippled_2BUILD.html b/md__2____w_2rippled_2rippled_2BUILD.html index cbe93b18ec..56c503cd34 100644 --- a/md__2____w_2rippled_2rippled_2BUILD.html +++ b/md__2____w_2rippled_2rippled_2BUILD.html @@ -151,20 +151,25 @@ Patched recipes
conan remote add --index 0 xrplf https://conan.ripplex.io

Alternatively, you can pull the patched recipes into the repository and use them locally:

cd external
+
mkdir -p conan-center-index
+
cd conan-center-index
git init
git remote add origin git@github.com:XRPLF/conan-center-index.git
git sparse-checkout init
git sparse-checkout set recipes/ed25519
+
git sparse-checkout add recipes/grpc
git sparse-checkout add recipes/secp256k1
git sparse-checkout add recipes/snappy
git sparse-checkout add recipes/soci
git fetch origin master
git checkout master
-
conan export --version 2015.03 recipes/ed25519/all
-
conan export --version 0.7.0 recipes/secp256k1/all
-
conan export --version 1.1.10 recipes/snappy/all
-
conan export --version 4.0.3 recipes/soci/all
rm -rf .git
+
cd ../..
+
conan export --version 2015.03 external/conan-center-index/recipes/ed25519/all
+
conan export --version 1.72.0 external/conan-center-index/recipes/grpc/all
+
conan export --version 0.7.0 external/conan-center-index/recipes/secp256k1/all
+
conan export --version 1.1.10 external/conan-center-index/recipes/snappy/all
+
conan export --version 4.0.3 external/conan-center-index/recipes/soci/all

In the case we switch to a newer version of a dependency that still requires a patch, it will be necessary for you to pull in the changes and re-export the updated dependencies with the newer version. However, if we switch to a newer version that no longer requires a patch, no action is required on your part, as the new recipe will be automatically pulled from the official Conan Center.

‍[!NOTE] You might need to add --lockfile="" to your conan install command to avoid automatic use of the existing conan.lock file when you run conan export manually on your machine

@@ -281,12 +286,7 @@ Build and Test

To build Debug, in the next step, be sure to set -DCMAKE_BUILD_TYPE=Debug

For a single-configuration generator, e.g. Unix Makefiles or Ninja, you only need to run this command once. For a multi-configuration generator, e.g. Visual Studio, you may want to run it more than once.

Each of these commands should also have a different build_type setting. A second command with the same build_type setting will overwrite the files generated by the first. You can pass the build type on the command line with --settings build_type=$BUILD_TYPE or in the profile itself, under the section [settings] with the key build_type.

-

If you are using a Microsoft Visual C++ compiler, then you will need to ensure consistency between the build_type setting and the compiler.runtime setting.

-

When build_type is Release, compiler.runtime should be MT.

-

When build_type is Debug, compiler.runtime should be MTd.

-
conan install .. --output-folder . --build missing --settings build_type=Release --settings compiler.runtime=MT
-
conan install .. --output-folder . --build missing --settings build_type=Debug --settings compiler.runtime=MTd
-
+

  • Configure CMake and pass the toolchain file generated by Conan, located at $OUTPUT_FOLDER/build/generators/conan_toolchain.cmake.

    Single-config generators:

    Pass the CMake variable CMAKE_BUILD_TYPE and make sure it matches the one of the build_type settings you chose in the previous step.