Modify path handling in some build scripts to be closer to mbedtls #376
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!376
Loading…
Reference in a new issue
No description provided.
Delete branch "paths-mergeability-crypto"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mostly this aligns the Visual Studio templates with mbedtls and makes the handling of directories in
generate_visual_studio.plmore generic.There is no completeness goal in this pull request, only a goal of non-harmfulness (no semantic change).
LGTM
By the way over the long run perhaps we should have a rule about ordering of the components in
all.sh(could be as simple as lexical order, which would also naturally group build/check/test together). But that's obviously out of scope for this PR.I'm fine with the PR. There's one minor pre-existing issue, but I don't think it's worth rework, unless there's some being done anyway, so approving.
Minor - Pre-existing really, but the error message of
"Must but run from mbedTLS root or scripts dir"doesn't quite match the failure condition, which is if a required directory is not found, the script fails.I suggest the error message be changed to:
I checked the CI results and the only failures are in mbed-os tests, which are known and expected to fail at this point, so can be ignored for this PR. Therefore I'm removing "needs: ci" and labeling "ready for merge".