-
Notifications
You must be signed in to change notification settings - Fork 2k
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
examples: Move in RIOT/applications #18602
examples: Move in RIOT/applications #18602
Conversation
…example add microcoap example application
…ofix sixlowapp: fix small typo
…ll_commands sixlowapp: adapted to new shell handler prototype
ng_sniffer: added ng version of sniffer application
The constants names changed in the past: RIOT-OS@426170b
sixlowapp: rename thread related constants
…gnore git: added .gitignore, copied from RIOT
Provide an application for openwsn
openwsn: fix prototype for putchar
This application was not adapted to RIOT-OS#3162 and RIOT-OS#3188
…etif_default ng_sniffer: added ng_netif_default
Related and dependent on RIOT-OS#3555
…hell_uart ng_sniffer: use uart0 only for none newlib boards
…rm/remove-old-app sniffer: remove old application
…etwork_stack_apps remove apps belonging to the old network stack
Was accidentally removed and is also updated to current gnrc.
sniffer: re-add sniffer
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.
Trusting your documentation of how you integrated the commits. The code was already reviewed in the applications repo, so I'd say it will look good as well ;-).
Murdock still needs those |
You can use the |
See #18602 (comment) ;-) |
As my docker setup is still broken, and the script is much more efficient than looking through murdock outputs: could you run create-makefile-ci on your machine?
|
Perfect opportunity for me to try this. |
Mhhh |
Mhh.. can't push to your fork :( here's the patch
|
I used my well established vim macro after all, to generate the Makefile.ci from the Murdock output btw. The |
Ah wait, I forgot to blacklist the pic32 boards. :-/. |
* @} | ||
*/ | ||
|
||
#include <stdint.h> |
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.
Oh, it is an actual bug that the PIC32 (and the RISC-V) toolchain found an actual bug.
#include <stdint.h> | |
#include <stdint.h> | |
#include <stdio.h> |
(updated the patch post to remove the boards that failed due to the bug) |
8d54b11
to
59d184f
Compare
Thanks, all updated. Force-pushing to squash the late blacklist change right away so that we have a chance of getting a usable Murdock result for merging. |
All but the false-positive 'Error: Commit needs to be squashed: "53e91a13e3 Update RIOT submodule to 2019.01"' are green now. With the ACKs in and me also stating this is ready: @miri64, could you merge this with administrative powers? |
Done. |
Should we archive |
Yes, but maybe with RIOT-OS/applications#83 on top. |
Could you also unpin it? I don't think the pinning is justified any more (not that it'd have helped a lot when it was live.) |
Also done! :-) |
Contribution description
The RIOT-OS/applications repository is sitting very unnoticed, with few changes. It would be nice if we could claim that these are because RIOT is so stable, but build failures when updating RIOT show that we do have API changes every now and then.
These would be handled much more easily if we just had the applications here as part of the examples. They fit in nicely -- the applications from there are no more standalone applications than some examples we already have, for example the gnrc_border_router.
Testing procedure
Look at whether the applications make sense (I haven't), and see that they build (CI checks that) and work.
PR creation and evolution
This PR was created by moving around examples in the original repository and then merging with --allow-unrelated-histories. This ensures that git attribution keeps working. It should also allow existing PRs against the applications to just be reapplied (and even merged into) this tree, because git should detect the moves.
Still, given that examples currently fail, rather than relying on that, I'd rather replay the set of commits on a fixed version of the applications, based on RIOT-OS/applications#78. (Until then, this will stay a draft).
Related issues
[edit: added]