djsundog
/
circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
circuitpython/py/mkenv.mk

73 lines
1.6 KiB
Makefile
Raw Normal View History

Rework makefiles. Add proper dependency checking.
2014-01-24 04:05:30 -05:00
ifneq ($(lastword a b),b)
$(error These Makefiles require make 3.81 or newer)
endif
# Set TOP to be the path to get from the current directory (where make was
# invoked) to the top of the tree. $(lastword $(MAKEFILE_LIST)) returns
# the name of this makefile relative to where make was invoked.
#
# We assume that this file is in the py directory so we use $(dir ) twice
# to get to the top of the tree.
THIS_MAKEFILE := $(lastword $(MAKEFILE_LIST))
TOP := $(patsubst %/py/mkenv.mk,%,$(THIS_MAKEFILE))
# Turn on increased build verbosity by defining BUILD_VERBOSE in your main
# Makefile or in your environment. You can also use V=1 on the make command
# line.
ifeq ("$(origin V)", "command line")
BUILD_VERBOSE=$(V)
endif
ifndef BUILD_VERBOSE
BUILD_VERBOSE = 0
endif
ifeq ($(BUILD_VERBOSE),0)
Q = @
else
Q =
endif
# Since this is a new feature, advertise it
ifeq ($(BUILD_VERBOSE),0)
$(info Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.)
endif
various: Spelling fixes
2017-05-29 03:08:14 -04:00
# default settings; can be overridden in main Makefile
Rework makefiles. Add proper dependency checking.
2014-01-24 04:05:30 -05:00
PY_SRC ?= $(TOP)/py
BUILD ?= build
RM = rm
ECHO = @echo
Replace some Makefile commands with variables in py/mkenv.mk
2014-04-06 20:35:45 -04:00
CP = cp
MKDIR = mkdir
SED = sed
py: Update makefiles to use $(CAT) variable instead of hard coded "cat". The variable $(CAT) is initialised with the "cat" value in mkenv.mk like for the other command line tools (rm, echo, cp, mkdir etc). With this, for example, Windows users can specify the path of cat.exe.
2019-05-20 12:47:23 -04:00
CAT = cat
py: Update makefiles to use $(TOUCH) instead of hard coded "touch". The variable $(TOUCH) is initialized with the "touch" value in mkenv.mk like for the other command line tools (rm, echo, cp, mkdir etc). With this, for example, Windows users can specify the path of touch.exe.
2019-05-21 05:35:09 -04:00
TOUCH = touch
py/mkenv.mk: Change default PYTHON variable from "python" to "python3". This change makes it so that python3 is required by default to build MicroPython. Python 2 can be used by specifying make PYTHON=python2. This comes about due to a recent-ish change to PEP 394 that makes the python command more optional than before (even with Python 2 installed); see https://github.com/python/peps/commit/cd59ec03c8ff1e75089d5872520cd0706774b35b#diff-1d22f7bd72cbc900670f058b1107d426 Since the command python is no longer required to be provided by a distribution we need to use either python2 or python3 as commands. And python3 seems the obvious choice.
2019-01-31 02:22:12 -05:00
PYTHON = python3
py, mk: Revert change where build variables set with ?=. ?= operator does not do delayed expansion (unlike =).
2014-06-07 08:14:45 -04:00
AS = $(CROSS_COMPILE)as
CC = $(CROSS_COMPILE)gcc
py: Treat -m32 flag as part of CC, LD, etc. Indeed, this flag efectively selects architecture target, and must consistently apply to all compiles and links, including 3rd-party libraries, unlike CFLAGS, which have MicroPython-specific setting.
2015-08-29 14:13:07 -04:00
CXX = $(CROSS_COMPILE)g++
py, mk: Revert change where build variables set with ?=. ?= operator does not do delayed expansion (unlike =).
2014-06-07 08:14:45 -04:00
LD = $(CROSS_COMPILE)ld
OBJCOPY = $(CROSS_COMPILE)objcopy
SIZE = $(CROSS_COMPILE)size
STRIP = $(CROSS_COMPILE)strip
py: Allow to to build MicroPython as a static library. The whole current port gets slurped into a static lib named "libmicropython.a". Maybe that's not ideal, but at least something to start with.
2015-10-12 07:42:05 -04:00
AR = $(CROSS_COMPILE)ar
py: Treat -m32 flag as part of CC, LD, etc. Indeed, this flag efectively selects architecture target, and must consistently apply to all compiles and links, including 3rd-party libraries, unlike CFLAGS, which have MicroPython-specific setting.
2015-08-29 14:13:07 -04:00
ifeq ($(MICROPY_FORCE_32BIT),1)
CC += -m32
CXX += -m32
LD += -m32
endif
Rework makefiles. Add proper dependency checking.
2014-01-24 04:05:30 -05:00
py/mkenv.mk: Use $(PYTHON) consistently when calling Python tools. Rationale: * Calling Python build tool scripts from makefiles should be done consistently using `python </path/to/script>`, instead of relying on the correct she-bang line in the script [1] and the executable bit on the script being set. This is more platform-independent. * The name/path of the Python executable should always be used via the makefile variable `PYTHON` set in `py/mkenv.mk`. This way it can be easily overwritten by the user with `make PYTHON=/path/to/my/python`. * The Python executable name should be part of the value of the makefile variable, which stands for the build tool command (e.g. `MAKE_FROZEN` and `MPY_TOOL`), not part of the command line where it is used. If a Python tool is substituted by another (non-python) program, no change to the Makefiles is necessary, except in `py/mkenv.mk`. * This also solves #3369 and #1616. [1] There are systems, where even the assumption that `/usr/bin/env` always exists, doesn't hold true, for example on Android (where otherwise the unix port compiles perfectly well).
2017-10-31 12:19:12 -04:00
MAKE_FROZEN = $(PYTHON) $(TOP)/tools/make-frozen.py
py/mkenv.mk: Use $(TOP) instead of ".." to reference tools, mpy-cross.
2017-05-19 01:53:55 -04:00
MPY_CROSS = $(TOP)/mpy-cross/mpy-cross
py/mkenv.mk: Use $(PYTHON) consistently when calling Python tools. Rationale: * Calling Python build tool scripts from makefiles should be done consistently using `python </path/to/script>`, instead of relying on the correct she-bang line in the script [1] and the executable bit on the script being set. This is more platform-independent. * The name/path of the Python executable should always be used via the makefile variable `PYTHON` set in `py/mkenv.mk`. This way it can be easily overwritten by the user with `make PYTHON=/path/to/my/python`. * The Python executable name should be part of the value of the makefile variable, which stands for the build tool command (e.g. `MAKE_FROZEN` and `MPY_TOOL`), not part of the command line where it is used. If a Python tool is substituted by another (non-python) program, no change to the Makefiles is necessary, except in `py/mkenv.mk`. * This also solves #3369 and #1616. [1] There are systems, where even the assumption that `/usr/bin/env` always exists, doesn't hold true, for example on Android (where otherwise the unix port compiles perfectly well).
2017-10-31 12:19:12 -04:00
MPY_TOOL = $(PYTHON) $(TOP)/tools/mpy-tool.py
py: Move frozen modules rules from esp8266 port for reuse across ports. A port now just needs to define FROZEN_DIR var and add $(BUILD)/frozen.c to SRC_C to support frozen modules.
2016-09-17 13:57:43 -04:00
Rework makefiles. Add proper dependency checking.
2014-01-24 04:05:30 -05:00
all:
.PHONY: all
Have make remove targets if a recipie fails.
2014-04-16 11:09:59 -04:00
.DELETE_ON_ERROR:
Rework makefiles. Add proper dependency checking.
2014-01-24 04:05:30 -05:00
MKENV_INCLUDED = 1