docs: update embed path to absolute due to build-static.sh changes#2064
Closed
docs: update embed path to absolute due to build-static.sh changes#2064
Conversation
alexandre-daubois
approved these changes
Dec 8, 2025
Member
|
LGTM, but what could be even better is to add back support for relative paths (by transforming it in an absolute path in the shell script 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
4 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.
The docs still show relative paths for
embed=. However, since the changes inbuild-static.sh, relative paths may not work reliably.I hit this issue while following the docs, so this PR updates the examples to use absolute paths.