-
Notifications
You must be signed in to change notification settings - Fork 7.7k
docs(c++): std::filesystem is generally supported (#5003) (IDFGH-12755) #13736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Hello nebkat, we appreciate your contribution to this project! 📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more. 🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project. Click to see more instructions ...
Review and merge process you can expect ...
|
sha=cae6a35ac71eb827024c6e46c7ad4512567b1658 |
@nebkat Thanks for the PR! In #5003 you wrote,
Do you recall what were the "some unusual cases in path concatenation"? We probably need to add some tests if we want to claim that std::filesystem is supported, so I'm wondering if we should check something specific. |
Actually we found that some functions used by std::filesystem aren't implemented in IDF, resulting in linker errors. For example, |
I believe the issue I encountered was with copying For |
@nebkat Here is my current changeset on top of your commit. You can see the few added stub functions there. esp-idf-13cf3f6-333f1db.patch.txt We will take a look at _GLIBCXX_HAVE_DIRFD and other config options. Not all of the current settings seem to make sense to me. |
Ironically
|
@nebkat Yep, my patch above should fix these linking issues. |
Thanks for the PR, have merged along with other changes in 3765290 |
Thanks for getting this over the line, great to see! |
Have been using most
std::filesystem
features successfully since IDF v5.1, and nowstd::filesystem::directory_iterator
is also fixed since 994b4ed.