Closed ghost closed 4 years ago
For the first problem, it seems like the C-compiler is more strict than it needs to be. I currently don't have access to a Windows machine to test this on, so I can't test the fix just yet, but it's probably just that -std=c99
has to be added to the compile flags in setup.py
: https://github.com/99991/matting/blob/master/setup.py#L27
flags = "-O3 -Wall -Wextra -pedantic -shared -std=c99"
For the second problem, the exception should probably just be a warning instead.
I'll see if I can get it fixed next weekend, but until then, you can try the successor library instead which has been released a few minutes ago.
The successor library works incredibly well! What great timing haha. Thank you so much.
The only thing is that in the 'run_tests.py' I had to change line 38 to simply
command = "python " + filename
otherwise I was getting some errors that the file path was invalid. Let me know if you want me to open an issue on that repo.
Also, tests 9 and 10 failed, but I think that is because I do not have a gpu, and the resulting matting does not seem affected.
Thanks again!!
Thank you for those kind words, that's great to hear!
The GPU foreground estimation tests will indeed fail if no GPU support is available. But maybe we should make the error message indicate that this is as expected.
Also thank you for your tip with line 38, will be fixed soon.
When running 'python setup.py install', I get the following output:
I saw elsewhere you mentioned that vcycle should still work without the libmatting library, but when I run 'from matting import vcycle' I get the following error:
Any advice?
Thanks!