-
Notifications
You must be signed in to change notification settings - Fork 44
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
Build fails on MacOS: new release needed? #137
Comments
We're planning to publish a new release during the Christmas holidays. |
W00t! Well, don't let it get in the way of Christmas relaxation. :-) I should add that this package has been very helpful in the toy project I'm working on, and I hope to find opportunities to make contributions as time allows. |
Hi @basvandijk and @purcell, I should have some more time to work on my project which is using I see there hasn't been too much activity on the repo lately, what's your statuses? |
Nothing new on my side, but I think a new release is still needed. In the meantime I'm using Stack to build against the dev version: extra-deps:
- inline-c-0.7.0.1@sha256:dece4a0d587e21b8c8987619ffeeab5da3c4c55db47d6ddf4568d7adaa05d5c1
- inline-c-cpp-0.3.0.1@sha256:916ffd22c097f399a47f6ddb9313e2ce36d8051755dd702c23f8d20a370fee09
- git: https://github.com/LumiGuide/haskell-opencv.git
commit: 0d0c1cbe2dd8e7705f6785c8bd4645cd18faebfb
subdirs: [ opencv ] Note also that OpenCV 3.x is needed, so now on MacOS with Homebrew it's necessary to
|
With the latest Stack and Stackage LTS, building via the above method no longer works, sadly:
I wonder if the dummy symlink is necessary, since that's what appears to be the problem. Alternatively, could you cut a new release on Hackage at this stage? |
Hi! I naïvely tried to use
opencv
0.0.2.1 in a Stack project on MacOS, and while compilation looked to be going well, it failed with the following error:This was on MacOS 10.14.2, with OpenCV 3.4.3_2 from homebrew, stack resolver
lts-12.24
, and extra-deps as follows:It looks like this was perhaps the issue reported in #121 and fixed in #122, and indeed by depending on the git version of
opencv
it looks like I've got things working, but perhaps you'd consider pushing a new release so that's not necessary?The text was updated successfully, but these errors were encountered: