Skip to content

examples: Move in RIOT/applications#18602

Merged
miri64 merged 153 commits into
RIOT-OS:masterfrom
chrysn-pull-requests:move-in-riot-applications
Sep 20, 2022
Merged

examples: Move in RIOT/applications#18602
miri64 merged 153 commits into
RIOT-OS:masterfrom
chrysn-pull-requests:move-in-riot-applications

Conversation

@chrysn

@chrysn chrysn commented Sep 16, 2022

Copy link
Copy Markdown
Member

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]

OlegHahm and others added 30 commits November 6, 2014 22:30
…example

add microcoap example application
…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
This application was not adapted to
RIOT-OS#3162 and
RIOT-OS#3188
…etif_default

ng_sniffer: added ng_netif_default
…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.

@miri64 miri64 left a comment

Copy link
Copy Markdown
Member

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 ;-).

@maribu maribu changed the title Move in RIOT/applications examples: Move in RIOT/applications Sep 20, 2022
@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Murdock still needs those Makefile.cis :-)

@miri64 miri64 added Process: needs >1 ACK Integration Process: This PR requires more than one ACK and removed Process: needs >1 ACK Integration Process: This PR requires more than one ACK labels Sep 20, 2022
@benpicco

benpicco commented Sep 20, 2022

Copy link
Copy Markdown
Contributor

You can use the make create-Makefile.ci target

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

You can use the make create-Makefile.ci target

See #18602 (comment) ;-)

@chrysn

chrysn commented Sep 20, 2022 via email

Copy link
Copy Markdown
Member Author

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

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.

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Mhhh examples/sniffer is throwing Deprecated modules are in use: shell_commands now that #18355 is merged ^^"

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Mhh.. can't push to your fork :( here's the patch

From 86cd3f55d6e63a8ba7bc6d31c4557de9f3e2f01c Mon Sep 17 00:00:00 2001
From: Martine Lenders <m.lenders@fu-berlin.de>
Date: Tue, 20 Sep 2022 13:29:39 +0200
Subject: [PATCH] examples: sniffer / spectrum_analyzer: amend Makefile.ci

---
 examples/sniffer/Makefile.ci          | 25 +++++++++++++++++++++++++
 examples/spectrum-scanner/Makefile.ci | 23 +++++++++++++++++++++++
 2 files changed, 48 insertions(+)
 create mode 100644 examples/sniffer/Makefile.ci
 create mode 100644 examples/spectrum-scanner/Makefile.ci

diff --git a/examples/sniffer/Makefile.ci b/examples/sniffer/Makefile.ci
new file mode 100644
index 0000000000..4b03fc1ce2
--- /dev/null
+++ b/examples/sniffer/Makefile.ci
@@ -0,0 +1,25 @@
+BOARD_INSUFFICIENT_MEMORY := \
+    arduino-duemilanove \
+    arduino-leonardo \
+    arduino-mega2560 \
+    arduino-nano \
+    arduino-uno \
+    atmega328p-xplained-mini \
+    atmega328p \
+    bluepill-stm32f030c8 \
+    i-nucleo-lrwan1 \
+    nucleo-f030r8 \
+    nucleo-f031k6 \
+    nucleo-f042k6 \
+    nucleo-l011k4 \
+    nucleo-l031k6 \
+    nucleo-l053r8 \
+    samd10-xmini \
+    slstk3400a \
+    stk3200 \
+    stm32f030f4-demo \
+    stm32f0discovery \
+    stm32g0316-disco \
+    stm32l0538-disco \
+    waspmote-pro \
+    #
diff --git a/examples/spectrum-scanner/Makefile.ci b/examples/spectrum-scanner/Makefile.ci
new file mode 100644
index 0000000000..613af759a7
--- /dev/null
+++ b/examples/spectrum-scanner/Makefile.ci
@@ -0,0 +1,23 @@
+BOARD_INSUFFICIENT_MEMORY := \
+    arduino-duemilanove \
+    arduino-leonardo \
+    arduino-nano \
+    arduino-uno \
+    atmega328p-xplained-mini \
+    atmega328p \
+    bluepill-stm32f030c8 \
+    i-nucleo-lrwan1 \
+    nucleo-f030r8 \
+    nucleo-f031k6 \
+    nucleo-f042k6 \
+    nucleo-l011k4 \
+    nucleo-l031k6 \
+    nucleo-l053r8 \
+    samd10-xmini \
+    slstk3400a \
+    stk3200 \
+    stm32f030f4-demo \
+    stm32f0discovery \
+    stm32g0316-disco \
+    stm32l0538-disco \
+    #
-- 
2.37.3

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

I used my well established vim macro after all, to generate the Makefile.ci from the Murdock output btw. The create-Makefile.ci took a) way too long and b) also showed errors for me.

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Ah wait, I forgot to blacklist the pic32 boards. :-/.

* @}
*/

#include <stdint.h>

Copy link
Copy Markdown
Member

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.

Suggested change
#include <stdint.h>
#include <stdint.h>
#include <stdio.h>

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

(updated the patch post to remove the boards that failed due to the bug)

@chrysn chrysn force-pushed the move-in-riot-applications branch from 8d54b11 to 59d184f Compare September 20, 2022 11:46
@chrysn

chrysn commented Sep 20, 2022

Copy link
Copy Markdown
Member Author

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.

@chrysn

chrysn commented Sep 20, 2022

Copy link
Copy Markdown
Member Author

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?

@miri64 miri64 merged commit c107d73 into RIOT-OS:master Sep 20, 2022
@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Done.

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Should we archive RIOT-OS/applications now that these apps are in?

@chrysn

chrysn commented Sep 20, 2022

Copy link
Copy Markdown
Member Author

Yes, but maybe with RIOT-OS/applications#83 on top.

@chrysn chrysn deleted the move-in-riot-applications branch September 20, 2022 14:59
@chrysn

chrysn commented Sep 20, 2022

Copy link
Copy Markdown
Member Author

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.)

@miri64

miri64 commented Sep 20, 2022

Copy link
Copy Markdown
Member

Also done! :-)

@maribu maribu added this to the Release 2022.10 milestone Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: doc Area: Documentation Area: examples Area: Example Applications CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Process: needs >1 ACK Integration Process: This PR requires more than one ACK

Projects

None yet

Development

Successfully merging this pull request may close these issues.