summaryrefslogtreecommitdiffstatshomepage
path: root/py
diff options
context:
space:
mode:
authorPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-03-30 00:08:27 +0300
committerPaul Sokolovsky <pfalcon@users.sourceforge.net>2017-03-30 00:08:27 +0300
commit29dd92c82a6ea07f8d4f71c5c6d18c45ccefde39 (patch)
tree4edc1589a6d7a8c0dc5237396792947eae32cff3 /py
parente9d7c3ea0ef7b726b093b1abf9cece0c9146d635 (diff)
downloadmicropython-29dd92c82a6ea07f8d4f71c5c6d18c45ccefde39.tar.gz
micropython-29dd92c82a6ea07f8d4f71c5c6d18c45ccefde39.zip
zephyr/Makefile: Rework to use modern, official build integration.
Build happens in 3 stages: 1. Zephyr config header and make vars are generated from prj.conf. 2. libmicropython is built using them. 3. Zephyr is built and final link happens.
Diffstat (limited to 'py')
-rw-r--r--py/mkrules.mk7
1 files changed, 7 insertions, 0 deletions
diff --git a/py/mkrules.mk b/py/mkrules.mk
index bc6389144b..2ba57e0eec 100644
--- a/py/mkrules.mk
+++ b/py/mkrules.mk
@@ -142,8 +142,15 @@ clean-prog:
endif
LIBMICROPYTHON = libmicropython.a
+
+# We can execute extra commands after library creation using
+# LIBMICROPYTHON_EXTRA_CMD. This may be needed e.g. to integrate
+# with 3rd-party projects which don't have proper dependency
+# tracking. Then LIBMICROPYTHON_EXTRA_CMD can e.g. touch some
+# other file to cause needed effect, e.g. relinking with new lib.
lib $(LIBMICROPYTHON): $(OBJ)
$(AR) rcs $(LIBMICROPYTHON) $^
+ $(LIBMICROPYTHON_EXTRA_CMD)
clean:
$(RM) -rf $(BUILD) $(CLEAN_EXTRA)