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
cpu/mips: deprecate mips cpu #17304
cpu/mips: deprecate mips cpu #17304
Conversation
@@ -50,4 +50,11 @@ else | |||
$(shell $(COLOR_ECHO) "$(COLOR_RED)Deprecated modules are in use:$(COLOR_RESET)"\ | |||
"$(DEPRECATED_MODULES_USED)" 1>&2) | |||
endif | |||
# Warn about used deprecated boards |
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.
I'm not sure this isn't going to cause trouble. does it print when doing, e.g., "BOARD=6lowpan-clicker make info-modules"?
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.
True, I guarded it with ifneq ($(RIOT_CI_BUILD),1)
, which should help against automated checks. For the developer just looking at it I don't think the warnings are a problem.
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.
Yep, same thing is done for BOARDSDIR already this makes sense
murdock passes... may I squash? |
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.
~~Please suqash!~~talked too fast
@@ -50,4 +50,13 @@ else | |||
$(shell $(COLOR_ECHO) "$(COLOR_RED)Deprecated modules are in use:$(COLOR_RESET)"\ | |||
"$(DEPRECATED_MODULES_USED)" 1>&2) | |||
endif | |||
# Warn about used deprecated boards | |||
include $(RIOTMAKE)/deprecated_boards.inc.mk |
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.
Does this need to run here? Couldn't it be done in Makefile.include
? Also can we make it only show up once with:
# Do not warn when set from sub-make
ifeq ($(MAKELEVEL),0)
...
endif
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.
makes sense
I see the call twice when building in docker, but I think that's fine otherwise I get the warning with the shinny red color, and no warning with RIOT_CI_BUILD=1 |
LGTM Ok to squash on my side, @kaspar030? |
Hmm I guess the |
Yes but improove later! |
Please squash! |
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.
ACK!
dad949c
to
8ae4f61
Compare
Done, thanks for the review. |
8ae4f61
to
6e1b4d1
Compare
9003d91
to
3b2f324
Compare
Add deprecate note in the mips cpu. Add warning in make when any mips based board is being used (6lowpan-clicker, pic32-wifire).
3b2f324
to
cf74b26
Compare
Enabled auto-merge, go! |
Contribution description
Add deprecate note in the mips cpu.
Add warning in make when any mips based board is being used (6lowpan-clicker, pic32-wifire).
After some discussion on the forum and between some maintainers we have decided to drop mips cpu as nobody is willing to continue to maintain it.
Testing procedure
Read the docs and run:
then check for the error messages.
Issues/PRs references
Related to #11788
[Forum post discussing dropping mips] (https://forum.riot-os.org/t/dropping-support-of-outdated-poorly-supported-boards-and-modules/3343/19)