libxx: All cxx libraries move down one level

[W-M-R]

Note: Please adhere to Contributing Guidelines.

Summary

Since there are some patches that need to be loaded manually, the original method is rather confusing. Now these patches that need to be loaded manually are classified into various cxx library folders, and each dynamically downloaded cxx library is moved down one directory to make the directory structure clearer.

Impact

No

Testing

No

[nuttxpr]

[Experimental Bot, please feedback here]

No. This PR does not adequately meet the NuttX requirements. While it provides a brief summary, it lacks crucial details. Here's why:

• Insufficient Summary: "All cxx libraries move down one level" is vague. Why was this move necessary? What problem does it solve? What specific libraries are affected? What does "down one level" mean in terms of directory structure?
• Missing Issue References: Are there related NuttX or NuttX Apps issues that prompted this change? These should be linked.
• Impact Underexplored: Simply stating "No" for all impact categories is insufficient. Even seemingly simple changes can have unforeseen consequences. Consider build processes, dependencies, and potential compatibility issues. Justify why there's no impact in each area. For example, if there's no impact on the build, explain why moving the libraries doesn't affect build scripts or dependencies.
• Inadequate Testing: Stating "depends on another PR" isn't enough. While dependencies exist, this PR needs its own verification. Provide specific build host and target details, along with "before" and "after" logs demonstrating the change's effectiveness and the lack of unintended side effects. What happens if the other PR isn't merged? How is this PR tested independently?

In short, the PR needs to be significantly more detailed and self-contained to meet the NuttX requirements. It should clearly explain the motivation, implementation details, potential impact, and provide independent verification of its functionality.

[acassis]

Approved, but please include an explanatory message in the commit log as to why this was necessary?

[W-M-R]

Approved, but please include an explanatory message in the commit log as to why this was necessary?

OKey

[lupyuen]

Sorry I have to cancel the CI Check, there's a problem with CI Test:

• drivers/pipes: return after short write if buffer is full #14667 (comment)

[W-M-R]

Sorry I have to cancel the CI Check, there's a problem with CI Test:

• drivers/pipes: return after short write if buffer is full #14667 (comment)

Do we need to restart ci after the fix is ​​merged?

[lupyuen]

@W-M-R Hopefully not? Let us track down the root cause and figure out the impact. Thanks!

[lupyuen]

Sorry I cancelled the CI Check again, since there's a problem with CI Test:

• drivers/pipes: return after short write if buffer is full #14667 (comment)