Allow the uPy used by run-tests to be overridden #504
Conversation
with MICROPY_MP_PY envvar, in an analogous way to MICROPY_CPYTHON3 envvar. (the reason for this will be made clearer by a later PR)
In conjunction with micropython#504 this allows you to do things like: ```shell make -C unix clean && make -C unix test CC=gcc-4.7 ``` all from the top-level micropython directory :-) Something similar could probably be done for windows/Makefile too, but I don't have a cygwin setup to test with.
|
What's MICROPY_MP_PY supposed to mean? ;-) |
|
I dunno, I was just keeping "in sync" with the name of the variable already used in the code... Better suggestions willingly accepted ;-) |
|
...hmmm, IMHO this build failure makes no sense - I get the identical error on my local machine if I delete Possibly a glitch?! @pfalcon or @dpgeorge could you try restarting it for me please? |
|
Yeah, but can you please de-acronymize it? Is it "micropython mycropython python"? Random suggestion is "MICROPY_MICROPY", or if that's confusing, use MICROPY_MICROPY_EXE and MICROPY_CPYTHON3_EXE. |
|
Well, the error is "TypeError: expect bytes or str, not tuple", can you comment on that? |
|
restarted. |
|
I'd be happy with |
|
|
As discussed in micropython#504
As discussed in micropython#504
Allow the uPy used by run-tests to be overridden
with MICROPY_MICROPYTHON envvar, in an analogous way to MICROPY_CPYTHON3 envvar.
(the reason for this will be made clearer by a later PR)