-
Notifications
You must be signed in to change notification settings - Fork 1
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
osx compile issue #1
Comments
Hey Zach, would you mind telling which version of Armadillo, are you using. I was able to compile 3.6.0 and I fixed the "check" issue, but could not run ofxSequence, I get a compile error: Undefined symbols for architecture i386: .. and I could not figure this out. Thanks! |
I am using 3.4.4 I thin, for that issue, I altered this in config.hpp:
commenting out #define ARMA_USE_BLAS which seems to force armadillo to use accelerate framework and link properly. I've noticed that armadillo is compiled (via cmake or brew) to be 64 bit, so that might be the linking issue you are seeing. |
Thanks a bunch! Compiled the latest version, without any issues, now I have to figure out how this thing actually works :) |
Hei! Sorry for the late view but my life is quite busy right now. So, I',, close this issue, if you think there is a better way (open a branch?) let me know. |
this is more a problem with armadillo then ofxSequence, but I thought I'd post it here in case it's helpful:
openframeworks/openFrameworks#1728
armadillo conflicts with a header that OF is pushing on it.
I fixed this by hand changing all the instances of "check()" within armadillo, but there's probably some simple #undef trick people can use.
on the OF side, we'll investigate the conflict including armadillo in an osx project causes, and I might post an OSX specific version of ofxSequence up in a branch if it's helpful.
The text was updated successfully, but these errors were encountered: