sanchayanmaity/minix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
minix/lib/libmthread
History
Lionel Sambuc fbd82e76a4 Let the build system manage compilation flags 
Do not hardcode warning and optimisation flags, otherwise the
main options (i.e. DBG, CPPFLAGS) will not work as expected.

You can still provide specific default by using DBG?=<value>.

Doing so leaves the opportunity to override the setting from the
commandline, while the default value from the build system is
then ignored for that particular package.

When crosscompiling, and using build.sh, adding -V DBG=<value> has
this same effect as make DBG=<value>.

Change-Id: Ic610e4d33b945acad64571e1431f1814291e2d84
2013-03-08 09:41:49 +01:00
..
allocate.c ARM support for system libraries 2012-08-28 13:49:27 -04:00
attribute.c libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00
condition.c libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00
event.c retire PUBLIC, PRIVATE and FORWARD 2012-03-25 21:58:14 +02:00
global.h libmthread: add possibility to randomize scheduler 2013-01-11 09:18:35 +00:00
key.c libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00
Makefile Let the build system manage compilation flags 2013-03-08 09:41:49 +01:00
misc.c libmthread: add stack traces 2012-04-13 12:54:02 +00:00
mutex.c libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00
proto.h libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00
queue.c libmthread: add possibility to randomize scheduler 2013-01-11 09:18:35 +00:00
rwlock.c retire PUBLIC, PRIVATE and FORWARD 2012-03-25 21:58:14 +02:00
scheduler.c libmthread: don't always verify library initialization 2012-05-01 09:55:06 +00:00