docs: Update instructions how to (re)generate conan.lock file - #6070
Merged
Conversation
bthomee
added
the
Trivial
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #6070 +/- ##
=========================================
- Coverage 78.6% 78.6% -0.0%
=========================================
Files 818 818
Lines 68938 68938
Branches 8241 8241
=========================================
- Hits 54166 54163 -3
- Misses 14772 14775 +3 see 4 files with indirect coverage changes 🚀 New features to boost your workflow:
|
mathbunnyru
requested changes
Nov 24, 2025
mathbunnyru
approved these changes
Nov 26, 2025
bthomee
enabled auto-merge (squash)
November 26, 2025 17:04
beartec-jpg
pushed a commit
to beartec-jpg/FalconLedger
that referenced
this pull request
Jun 1, 2026
…6070) This change updates the instructions for how to generate a Conan lockfile that is compatible with Linux, macOS, and Windows. Whenever Conan dependencies change, the Conan lock file needs to be regenerated. However, different OSes have slightly different requirements, and thus require slightly different dependencies. Luckily a single `conan.lock` file can be used, as long as the union of dependencies is included. The current instructions in the `BUILD.md` file are insufficient to regenerate the lock file such that it is compatible with all OSes, which this change addresses. The three profiles contain the bare minimum needed to generate the lockfile; it does not particularly matter whether the build type is Debug or Release, for instance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
High Level Overview of Change
This change updates the instructions for how to generate a Conan lockfile that is compatible with Linux, macOS, and Windows.
Context of Change
Whenever Conan dependencies change, the Conan lock file needs to be regenerated. However, different OSes have slightly different requirements, and thus require slightly different dependencies. Luckily a single
conan.lockfile can be used, as long as the union of dependencies is included.The current instructions in the
BUILD.mdfile are insufficient to regenerate the lock file such that it is compatible with all OSes, which this change addresses. The three profiles contain the bare minimum needed to generate the lockfile; it does not particularly matter whether the build type is Debug or Release, for instance.Type of Change
.gitignore, formatting, dropping support for older tooling)