-
Couldn't load subscription status.
- Fork 250
missing import #563
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
base: master
Are you sure you want to change the base?
missing import #563
Conversation
```
$ python3 toolchain.py build zbarlight
...
Traceback (most recent call last):
File "toolchain.py", line 3, in <module>
main()
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 1519, in main
ToolchainCL()
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 1276, in __init__
getattr(self, args.command)()
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 1337, in build
build_recipes(args.recipe, ctx)
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 1127, in build_recipes
recipe.execute()
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 699, in execute
self.build_all()
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 73, in _cache_execution
f(self, *args, **kwargs)
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 793, in build_all
self.build(arch)
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 73, in _cache_execution
f(self, *args, **kwargs)
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/toolchain.py", line 780, in build
self.build_arch(arch)
File "/Users/mflaxman/workspace/kivy-ios/kivy_ios/recipes/zbarlight/__init__.py", line 38, in build_arch
shprint(hostpython, "setup.py", "build", # noqa: F821
NameError: name 'shprint' is not defined
```
Even with this bugfix I'm still getting an error, but it could be specific to my environment.
|
@mflaxman sorry for the delay. As you said, I see from the CI that the recipe it's still failing to build: As far as I can see, the Would you like to further investigate about it? |
Just about to PR that :-) |
Even with this bugfix I'm still getting an error, but it could be specific to my environment.