-
Notifications
You must be signed in to change notification settings - Fork 90
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
Mac OS X support #30
Comments
The core runtime, along with ROS bridge and (Python) interop is .NET Standard, and so is supported on MacOS X as well as Linux and Windows. The major areas of componentry (e.g. imaging, media, speech, ...) also have cross-plat assemblies at least for standard message types, but then each have platform-specific components (. Sadly, MacOS lags behind here. We've tried to be consistent in the naming of projects with For example, FWIW, my personal arrangement is VS Code on a MacBook for development. I run PsiStudio (which is Windows-only) in Parallels which works great. A lot of my work happens to be from recorded stores (gathered from deployed Linux/Windows systems) and so, not having source/sensor components for the Mac itself hasn't been much of an issue. Totally depends on your scenario. Hope this helps! |
This helped a lot. Similar to your setup, we are using a Windows system to record data from sensors to a data store. Then on Macs, we can replay the data just fine. One thing that took me a little while to figure out was the right types of projects to have in my solution. Here is what I ended up with:
Is this a reasonable setup? |
That sounds like a totally reasonable setup; very similar to what we do. Glad it’s working for you! |
Does /psi work well on Mac OS X? What are the limitations?
The text was updated successfully, but these errors were encountered: