[riot-notifications] [RIOT-OS/RIOT] core: provide main thread as optional default module (#10971)

Martine Lenders notifications at github.com
Fri Feb 8 12:25:16 CET 2019

The RIOT community cares a lot about code quality.
Therefore, before describing what your contribution is about, we would like
you to make sure that your modifications are compliant with the RIOT
coding conventions, see https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions.

### Contribution description
For a private project of mine I did not really need the main thread. At most I needed [it for some device-setup](https://github.com/miri64/RIOT_playground/blob/a02ca4e157e5afcb6e148103d7626271a585a3a2/wand/main.c#L274-L287) (I will also provide a feature to do that without `main()` that), but the rest was basically happening in ISR (or for other applications the action might happen in other threads). While it isn't really necessary for my specific case, as the board has a large enough memory, to cope with that, but basically I am wasting a lot of memory, just for simple initialization. As such I am wondering if we could provide a mechanism to completely remove the main-thread and is stack. This is my proposal for that.
Put here the description of your contribution:
- describe which part(s) of RIOT is (are) involved
- if it's a bug fix, describe the bug that it solves and how it is solved
- you can also give more information to reviewers about how to test your changes

### Testing procedure
All applications should still compile and work as before. When compiling with `DISABLE_MODULE=core_main` most applications should still compile, they might not work properly anymore, but they should be significantly smaller.
Details steps to test your contribution:
- which test/example to compile for which board and is there a 'test' command
- how to know that it was not working/available in master
- the expected success test output

### Issues/PRs references
Requires 10970
Examples: Fixes #1234. See also #5678. Depends on PR #9876.

Please use keywords (e.g., fixes, resolve) with the links to the issues you
resolved, this way they will be automatically closed when your pull request
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.

You can view, comment on, or merge this pull request online at:


-- Commit Summary --

  * make: Allow for true pseudo-submodules
  * core: provide main thread as optional default module

-- File Changes --

    M Makefile.base (2)
    M core/kernel_init.c (10)
    M makefiles/defaultmodules.inc.mk (2)

-- Patch Links --


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190208/e46e4655/attachment.html>

More information about the notifications mailing list