-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Dlib master & 19.19 and later - build failed on MacOS/clang 10/cmake 3.17.1 #2061
Comments
Does doing what #2009 suggests fix it? |
Unfortunately not.
|
¯_(ツ)_/¯ Seems like a bug in cmake or something. I don't have a way to reproduce this, so you will need to figure out a workaround. And post a PR when you figure it out :) |
Yes, it seems like a bug in Cmake. My workaround is quite simple but it's not a solution - comment out lines 74-85 of dlib/cmake_utils/use_cpp_11.cmake |
Huh. It seems like there should be a better way. It would be a bit surprising if |
Warning: this issue has been inactive for 35 days and will be automatically closed on 2020-06-06 if there is no further activity. If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search. |
Warning: this issue has been inactive for 43 days and will be automatically closed on 2020-06-06 if there is no further activity. If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search. |
Notice: this issue has been closed because it has been inactive for 45 days. You may reopen this issue if it has been closed in error. |
The text was updated successfully, but these errors were encountered: