-
Notifications
You must be signed in to change notification settings - Fork 96
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
Add shared-state-async network statistics sharing #1087
Conversation
5d6ee3c
to
0cfd1e6
Compare
This stuff (and in general what is meant for mesh-wide milestone) is developed on top (and depends) on OpenWrt development branch, as an example |
other even more retro-compatibility breaking stuff is coming to out of my experimentation to have better support for newer radios https://www.youtube.com/live/DOH5FBMTXmE?feature=shared&t=10848 |
Ok, will it work at least on OpenWrt 23? |
AFAIU it will not work on OpenWrt 23 either, @javierbrk tried to compile and failed because of not enough recent compiler AFAIR Better creating a branch for the planned release and backport there stuff if needed, while development keep staying on master branch |
Ok, please create a branch with the code you know will work with OpenWrt 23. |
Ain't got time for that last compatible commit should be this a5eb7d8 |
I compiled shared-state-async from a823f47 for OpenWrt 23.05.2 and it is working. |
Hi ! My compilation errors were using gcc 11 shipped with openwrt 22.03 !
Saludos
Ing. Javier Alejandro Jorge
…On Mon, 26 Feb 2024 at 14:24, pony1k ***@***.***> wrote:
AFAIU it will not work on OpenWrt 23 either, @javierbrk
<https://github.com/javierbrk> tried to compile and failed because of not
enough recent compiler AFAIR
I compiled shared-state-async from a823f47
<a823f47>
for OpenWrt 23.05.2 and it is working.
—
Reply to this email directly, view it on GitHub
<#1087 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABE2I2CH4VND7XYCKFWIRD3YVTAN5AVCNFSM6AAAAABDUTR45CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUG4YDENBWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Good news! So we can go ahead without dealing with multiple branches for now |
No description provided.