Posted: Sun Apr 27, 2008 11:21 am
I just cannot believe what I've just seen. To restore compliance with OIS 1.0RC1, I downloaded and tested it --> doesn't compile.
The reason is quite simple. v1.0 has a method called numKeyboards(), v1.0RC1 has one called numKeyBoards(). The same goes for numJoySticks() resp. numJoysticks().
Unfortunately both versions are versioned 1.0.0, codename "nitro". I'm not sure whether I can resolve this.
EDIT: That's really going to be tricky. The only way to make it portable automatically is with CMake. But that's not very easy since I would have to read the appropriate header file (one of 7 that are different; diffed them all...) and compare the string lengths.
EDIT2: fabian suggested to simply build ois with orxonox. That makes things a lot easier for me: The version is always 1.2 and I can update whenever a new version releases without having to bother about compatibility. OIS by the way is only 270KB heavy, just if you're wondering.
Anyway, OIS compiles right now, but I couldn't test it on linux yet.
The reason is quite simple. v1.0 has a method called numKeyboards(), v1.0RC1 has one called numKeyBoards(). The same goes for numJoySticks() resp. numJoysticks().
Unfortunately both versions are versioned 1.0.0, codename "nitro". I'm not sure whether I can resolve this.
EDIT: That's really going to be tricky. The only way to make it portable automatically is with CMake. But that's not very easy since I would have to read the appropriate header file (one of 7 that are different; diffed them all...) and compare the string lengths.
EDIT2: fabian suggested to simply build ois with orxonox. That makes things a lot easier for me: The version is always 1.2 and I can update whenever a new version releases without having to bother about compatibility. OIS by the way is only 270KB heavy, just if you're wondering.
Anyway, OIS compiles right now, but I couldn't test it on linux yet.