-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Recipes #459
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
Recipes #459
Conversation
Great, thanks. Do the pypi ones definitely need recipes? I know they do in p4a master, but I'm not sure why they can't be installed by pip. |
They shouldn't need recipes (I'm running a test now to check), but currently any recipe that wants to depend on them will require them. The Twisted app I want to get running depends on all of the above. |
Okay, makes sense. |
IMHO if #449 is an easy fix, then we don't bother checking in the trivial recipes (and I'll remove the first commit from the PR). If it isn't, then we check them in for now and then drop them once they aren't necessary (and existing dependent recipes will not be affected, because the recipe names are the same as their PyPI names). |
And for the record, all three trivial recipes ( |
I won't let these recipes hold me up checking and merging the PRs, but indeed if it's an easy fix then I'l do it first and just remove them. Thanks though - as tito remarked when he did kivy-ios, redoing all the recipes is an annoying part! |
I'm happy to get the various recipes relevant to me into a state as close to working as I can, which should make your job easier (only having to spot my stupid mistakes 😛), and provide additional data points for testing the toolchain 😄 For now I'll stick to recipes I need that I think are generally helpful, since all recipes currently need to be in the core codebase until support for user-defined recipes is ready. |
Great, thanks! |
More recipes. All recipes appear to build correctly (except maybe pyOpenSSL), but for some reason, the OpenSSL recipe causes problems in SDL2:
The problem remains even if I remove the modification to the Python2 recipe (so therefore the OpenSSL recipe should be completely independent of the SDL2 one). However, if I run a build that does not contain
--requirements openssl
(or anything with a dependency on it) then the SDL2 recipe builds fine even with the Python2 recipe modifications.