8000 Automatic (re)building of mpy-cross negatively affects development cycle · Issue #3255 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

Automatic (re)building of mpy-cross negatively affects development cycle #3255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
pfalcon opened this issue Aug 5, 2017 · 4 comments
Closed

Automatic (re)building of mpy-cross negatively affects development cycle #3255

pfalcon opened this issue Aug 5, 2017 · 4 comments
Assignees
@dpgeorge

Comments

@pfalcon
Copy link
Contributor
pfalcon commented Aug 5, 2017

Ever since mpy-cross started to build automatically on "make" (e.g. on unix) port, there's additional (2x or more) wait time on each change to rebuild it. This makes development more cumbersome. There should be a special make target to build just local upy binary, without updating mpy-cross, or some other workaround.
@dpgeorge
Copy link
Member

or some other workaround.

The issue is not the mpy-cross dependency but rather the frozen bytecode dependency. And it's possible to remove this dependency (and hence not build mpy-cross0:

$ make FROZEN_MPY_DIR=

That will (or at least should) work for all ports. Though it may require a fresh build the first time, since it changes mpconfig.h options.

@pfalcon
Copy link
Contributor Author
pfalcon commented Aug 17, 2017

The issue is not the mpy-cross dependency but rather the frozen bytecode dependency.

I'm not sure I agree. I'm fine with bytecode dependency, and would like to build executable as configured in mainline (e.g. with upip frozen for unix port). What I wouldn't like is mpy-cross rebuilt on every sneeze, as probability that something affecting mpy-cross changed in current working session is low. Is there provision to ignore frozen bytecode's dependency on mpy-cross (i.e. make it all work like before, by passing something on the make command line) ?

@SpotlightKid
Copy link
Contributor
SpotlightKid commented Nov 29, 2017 •
edited
Loading

Any progress on this? Halving the typical compile time is a worthwhile goal IMO.

@dpgeorge dpgeorge mentioned this issue May 31, 2019
Closed
@dpgeorge
Copy link
Member
dpgeorge commented Jun 3, 2019

Resolved by 4173950

@dpgeorge dpgeorge closed this as completed Jun 3, 2019
@embeddedt embeddedt mentioned this issue Jun 20, 2019
Closed
@dpgeorge dpgeorge mentioned this issue Mar 15, 2020
Closed
tannewt pushed a commit to tannewt/circuitpython that referenced this issue Aug 11, 2020
@jepler
Merge pull request micropython#3255 from ciscorn/fix-rtd
ce911c5 
Fix Read the Docs bulid failing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dpgeorge dpgeorge

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pfalcon @SpotlightKid @dpgeorge
0