-
Notifications
You must be signed in to change notification settings - Fork 14
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
Does the plugin work for OSX 12, 13? #143
Comments
it should be ok, I am unsure it works with a M1 processor. (It is compile for Mac-intel, but might work with rosetta 2..) you need to exact same version of the plugin than the cubit you are using. can you tell me which version you are attempting to use so I can give it a try ? |
I just confirmed that the 2021.11 plugin work with MacOS 13.0.1 on a MAC-intel. @veeshy please let me know if you need me to check other build (or a M1-MAC). |
I’m on intel, 22.4 and downloaded the correct versions. Will try with 21.11 tomorrow just in case (edit: did not work either). Thanks for checking. Also might be my fault in multiple ways, do you need dagmc compiled first or is the cubit plugin standalone? |
Looked a little more at this, I see when using the cubit no gui cli the plugin load errors with:
Looking at the plugin library,
I don't have Is there some preqreq I missed? Is my osx jank? Interesting it works for you without any issues. |
wait.. why did I hack it in, clearly |
I have the same problem with 2022.4 I believe the is something broken in the build process. I probably know how to fix it. 2021.11 should with the the 2021.11 version of cubit (I did try it on my Mac-intel) it worked.
I'll try to issue a fix on 2022.4 and ping you on the PR |
I see the plugin builds for osx 11, is it supposed to work for other versions? It didn't work for me, but there weren't any lib errors, cubit simply didn't have the
dagmc
cmd available after copying the files into theMacOS/plugins/
folder.Perhaps related but the plugin dir in osx (left) and linux (right) builds has different files, is that expected?
The text was updated successfully, but these errors were encountered: