Conversation
- Removed unnecessary RPATH build option.
|
Well this is exciting, looking forward to trying it! |
|
Hi Jason, I tried adding the new opencv recipe folder to my kivy linux virtual machine. When building my app with the "buildozer android debug" command, using the packages "numpy,opencv,kivy" in buildozer.spec, I get the error (paraphrasing because I don't have it in front of me): Obviously, pip shouldn't be used in order to generate the opencv lib, since it's not a listed package. Any suggestions/tips on how I can include this recipe before your pull request is accepted? |
|
That's strange, when a recipe exists pip should not be activated to install that package, can you run: Also, did you set the |
|
I was suspicious of what directory is being used. I will investigate this, but it might be a couple days. This would certainly seem to explain the issue. Thanks for the response! |
|
The directory was indeed incorrect (pointing to default) I added the new OpenCV recipe folder to the /home/kivy/buildozer/.buildozer/android/platform/python-for-android/recipes/ path, ran it again, and got: |
|
I suggest to do the following:
|
|
using your p4a fork worked! It has built, now to see how it works compared to my PC kivy app! PIL had some problematic filter differences, so we'll see! |
|
Okay, it's working great! I have questions if you're willing to share how you used the android camera feature, but I'll save those for the the other thread about OpenCV support |
|
That's neat!!! |
This is a fully working recipe for OpenCV (v2.4.10.1). The recipe automatically builds OpenCV Python module (cv2.so) and installs native camera libraries. This recipe attempts to fix #75.