-
Notifications
You must be signed in to change notification settings - Fork 7
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
Linux and Mac OS X support #1
Comments
There is some code in the OSVR USBSerial library that might be useful in avoiding hard-coding the serial port. See also the |
Nice, ChristophHaag@a2303e1 works like a charm (on linux at least). Thanks for the tip. |
@ChristophHaag I'm glad it worked for you! If you're searching for a device with a known VID/PID, you can pass those values as arguments to |
Yes, that works better. It's a pretty limited iterator though, for example it doesn't implement the necessary stuff for std::distance to work, so you still have to manually iterate over the entries in order to count them. But that's not a big deal, works fine. For fswatch (I wrote fswatcher first, but that's another project without Mac OS X support so far) apparently you need to run autotools and configure first for the cmake project to work. Looks like that's going to be a bit of a hassle to set up to work on multiple operating systems in the cmake project. I tried it out with the library installed to the system (when the directory containing libfswatch/ is in the include path) and it seems to work fine. After the file is changed it prints |
Hello ChristophHaag@ Any chance to have your changes merged to this project? Best, |
I have not started to make pull requests, because several of these changes break the functionality on windows or are at least likely to not work on windows. |
Looks like a nice GUI that's "almost" cross platform already.
I started doing some changes here: https://github.com/ChristophHaag/OSVR-CPI/commits/master
Some random things:
thePort->waitForReadyRead(5000)
doesn't work on linux, it always returns false. Should only matter for the firmware update though.If anyone has some tips how to proceed I'd be happy to try them.
The text was updated successfully, but these errors were encountered: