-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Split toolchain.py into separate modules #526
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.
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
Conversation
9971d63
to
44a0e99
Compare
@kived I've split it up as seemed sensible - toolchain.py remains the entry point, build.py contains most of the building stuff, and mostly each of the other class types is split up into its own module. Does it look okay to you? (A few things remain to be done, like making each recipe import from the right submodule rather than via toolchain) |
Looks good to me! 👍 |
Great. I noticed a couple of small bugs today, but I'll fix them and merge later tonight. |
Provides backwards compatibility for recipes.
I fixed a bug with imports in the pygame recipe by importing them in toolchain.py (debug and ensure_dir). |
add missing code from previous pr
…into split_toolchain
Split toolchain.py into separate modules
Thanks, I don't know how I missed that previous PR. Looks good now though so I'll merge. |
This is a WIP, do not merge yet!
Opinions welcome, I'm not certain about the best way to make some of the splitting choices.