-
Notifications
You must be signed in to change notification settings - Fork 2.1k
sys/net/sock_util: Do not depend on network stack #21419
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice <3 this has been annoying me for some time!
This allows using and compiling the URL handling functions of sock_util without a network stack used. Co-authored-by: benpicco <benpicco@googlemail.com>
Co-authored-by: benpicco <benpicco@googlemail.com>
Thx :) |
This does break the build with lwIP - turns out we don't have this covered by CI 😕
|
I'll have a look later today |
#21467 should fix this |
@benpicco thanks for rapid response! |
I'm planing a simple client/server example for LWIP IPv4, which could serve as test for such situations. |
Contribution description
This allows using and compiling the URL handling functions of
sock_util
without a network stack used.Specifically, the URL splitting function can be useful even without having a network stack in use, e.g. for exotic CoAP transports (say, CoAP over SMS or CoAP over UART).
Testing procedure
The generated binaries should not change. But including
sock/util.h
without a network stack should now work without compilation failures.Issues/PRs references
Split out of #21048