RIOT/tests/pthread_cleanup/Makefile

APPLICATION = pthread_cleanup
include ../Makefile.tests_common

BOARD_BLACKLIST := arduino-mega2560 waspmote-pro arduino-uno arduino-duemilanove
# arduino mega2560 uno duemilanove : unknown type name: clockid_t

USEMODULE += pthread

include $(RIOTBASE)/Makefile.include
tests: fix APPLICATION name 2014-07-30 21:30:22 +02:00			`APPLICATION = pthread_cleanup`
posix: Add pthread_cleanup handlers With `pthread_cleanup_(push\|pop)` you can define a function that should be ran if the thread is exited while it is inside this scope. A thread can be ended here through an explicit call to `pthread_exit()`, or if cancellation was requested and a cancellation point was hit. `pthread_cleanup_*` is mostly only useful together with cancellation points, and cancellation points are only useful with a cleanup functionality. Cancellation points are at least partially implemented by means of `pthread_testcancel()`. C.f. ["Cancellation Points"][1]. [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09_05_02 2014-03-01 00:03:56 +01:00			`include ../Makefile.tests_common`

tests: adapt for arduino uno and duemilanove support - blacklist arduino-uno and arduino-duemilanove for coap, libfixmath_unittests, lwip, nhdp, pthread, pthread_barrier, pthread_cleanup, pthread_condition_variable pthread_cooperation, pthread_rwlock and pthread_tls tests. - fix sys/pipe build - unittests: boards added to BOARD_INSUFICIENT_MEMORY list. 2016-09-19 21:46:55 +02:00			`BOARD_BLACKLIST := arduino-mega2560 waspmote-pro arduino-uno arduino-duemilanove`
			`# arduino mega2560 uno duemilanove : unknown type name: clockid_t`
tests: blacklist failing test on arduino-mega2560 2014-07-15 12:11:04 +02:00
posix: Add pthread_cleanup handlers With `pthread_cleanup_(push\|pop)` you can define a function that should be ran if the thread is exited while it is inside this scope. A thread can be ended here through an explicit call to `pthread_exit()`, or if cancellation was requested and a cancellation point was hit. `pthread_cleanup_*` is mostly only useful together with cancellation points, and cancellation points are only useful with a cleanup functionality. Cancellation points are at least partially implemented by means of `pthread_testcancel()`. C.f. ["Cancellation Points"][1]. [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_09_05_02 2014-03-01 00:03:56 +01:00			`USEMODULE += pthread`

			`include $(RIOTBASE)/Makefile.include`