Skip to content

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

Merged
merged 22 commits into from
Dec 11, 2015
Merged

Split toolchain.py into separate modules #526

merged 22 commits into from
Dec 11, 2015

Conversation

inclement
Copy link
Member

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.

@inclement
Copy link
Member Author

@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)

@kived
Copy link
Contributor

kived commented Dec 11, 2015

Looks good to me! 👍

@inclement
Copy link
Member Author

Great. I noticed a couple of small bugs today, but I'll fix them and merge later tonight.

Provides backwards compatibility for recipes.
@kived
Copy link
Contributor

kived commented Dec 11, 2015

I fixed a bug with imports in the pygame recipe by importing them in toolchain.py (debug and ensure_dir).

inclement added a commit that referenced this pull request Dec 11, 2015
Split toolchain.py into separate modules
@inclement inclement merged commit eba92ab into master Dec 11, 2015
@inclement
Copy link
Member Author

Thanks, I don't know how I missed that previous PR. Looks good now though so I'll merge.

@inclement inclement deleted the split_toolchain branch December 11, 2015 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants