openmano-mpy/bare-arm/Makefile, branch master MicroPython source and hardware configuration for OpenMano ports: Make new ports/ sub-directory and move all ports there. 2017-09-06T03:40:51+00:00 Damien George 2017-09-06T03:40:51+00:00 01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 
This is to keep the top-level directory clean, to make it clear what is
core and what is a port, and to allow the repository to grow with new ports
in a sustainable way.
all: Make use of $(TOP) variable in Makefiles, instead of "..". 2017-08-11T02:22:19+00:00 Damien George 2017-08-11T02:22:19+00:00 7d4a2f773cc6ce24a91e2d210378188f3371e8a6 $(TOP) is defined in py/mkenv.mk and should be used to refer to the top level of this repository. 
$(TOP) is defined in py/mkenv.mk and should be used to refer to the top
level of this repository.
bare-arm/Makefile: Change C standard from gnu99 to c99. 2017-03-23T04:41:04+00:00 Damien George 2017-03-23T04:41:04+00:00 4afa782fb415165aa6e7f9eea8532f0d2493f8ce 






all/Makefile: Remove -ansi from GCC flags, its ignored anyway.
2017-03-23T04:32:12+00:00

Krzysztof Blazewicz

2017-03-05T12:28:27+00:00

75589272ef12d538ab7ce4f4453be85d826b5083

The -ansi flag is used for C dialect selection and it is equivalent to -std=c90.
Because it goes right before -std=gnu99 it is ignored as for conflicting flags
GCC always uses the last one.





The -ansi flag is used for C dialect selection and it is equivalent to -std=c90.
Because it goes right before -std=gnu99 it is ignored as for conflicting flags
GCC always uses the last one.







Makefiles: Remove duplicate object files when linking.
2015-10-24T12:46:53+00:00

Paul Sokolovsky

2015-10-23T23:26:10+00:00

0dbd928ceefed09d65276211c70d0137b4734011

Scenario: module1 depends on some common file from lib/, so specifies it
in its SRC_MOD, and the same situation with module2, then common file
from lib/ eventually ends up listed twice in $(OBJ), which leads to link
errors.

Make is equipped to deal with such situation easily, quoting the manual:
"The value of $^ omits duplicate prerequisites, while $+ retains them and
preserves their order." So, just use $^ consistently in all link targets.





Scenario: module1 depends on some common file from lib/, so specifies it
in its SRC_MOD, and the same situation with module2, then common file
from lib/ eventually ends up listed twice in $(OBJ), which leads to link
errors.

Make is equipped to deal with such situation easily, quoting the manual:
"The value of $^ omits duplicate prerequisites, while $+ retains them and
preserves their order." So, just use $^ consistently in all link targets.







all: Make netutils.h available to all ports by default.
2015-10-19T15:32:42+00:00

Paul Sokolovsky

2015-10-19T15:22:16+00:00

e0f5df579b6cf0410b9693f9a75d9b50a0de350e

Generally, ports should inherit INC from py.mk, append to it, not
overwrite it. TODO: Likely should do the same for other vars too.





Generally, ports should inherit INC from py.mk, append to it, not
overwrite it. TODO: Likely should do the same for other vars too.







bare-arm: Prefix includes with py/; remove need for -I../py.
2015-01-01T21:14:42+00:00

Damien George

2015-01-01T21:14:42+00:00

c2e22d66da3d0e18eace43e2705ee47e99431ae2












Makefiles: Support py/*.h includes per #1022.
2014-12-27T14:32:52+00:00

Paul Sokolovsky

2014-12-27T14:11:49+00:00

3b74c91684e6dfc785bf33ba03e520470f59059e












bare-arm: Enable link map file.
2014-06-27T18:02:04+00:00

Paul Sokolovsky

2014-06-27T15:58:31+00:00

0a1ea402739f400bb477e00dbc21c97feaec4fea

This port supposed to be demo of uPy minimality, so let people behold it in
details.





This port supposed to be demo of uPy minimality, so let people behold it in
details.







bare-arm, stmhal, teensy: Duplicate -nostdlib to CFLAGS
2014-06-18T11:34:07+00:00

Sven Wegener

2014-06-14T15:41:13+00:00

c3cabf4e336c104542bb248730094747b13977b1

As we are building with -nostdlib gcc features like the stack protector
will fail linking, because the failure handlers are in gcc's internal
libs. Such features are implicitly disabled during compilation when
-nostdlib is used in CFLAGS too.

Signed-off-by: Sven Wegener <sven.wegener@stealer.net>





As we are building with -nostdlib gcc features like the stack protector
will fail linking, because the failure handlers are in gcc's internal
libs. Such features are implicitly disabled during compilation when
-nostdlib is used in CFLAGS too.

Signed-off-by: Sven Wegener <sven.wegener@stealer.net>