Problems (#1) - Building (#40) - Message List
In short: Need help getting things set up so I can build CWiid.
Ok, I'm a programmer, but I'm relatively inexperienced with *nix. I had this all working before, but a hard drive died, I had to rebuild the system, and I can't seem to remember all of what I did.
Right now, I'm on a fresh install of Xubuntu 7.04. I did 'sudo apt-get install' for bison, flex and python, and apt-get reports I already have awk. I know there's still some requirements I'm missing (bluez-libs, gtk+-2 dev libs, uinput kernel support, and kernel sources, according to the readme), but I'm not sure how to get them.
FWIW, The following message is what I'm getting ATM when I try to configure:
checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
-
Message #176
Nevermind, I've gotten it. With some apt-get guessing, plus poking around in the package manager, etc., I got the packages I needed installed. IIRC, These are the ones I needed:
autoconf autogen automake g++ (gcc was already installed, but not g++) bluetooth libbluetooth2-dev libgtk2.0-dev pkg-config python2.5-dev
I might be forgetting a few.
Abscissa07/22/07 06:33:44 (6 years ago)-
Message #177
Hmm, line breaks don't seem to work unless there's two of them:
autoconf
autogen
automake
g++ (gcc was already installed, but not g++)
bluetooth
libbluetooth2-dev
libgtk2.0-dev
pkg-config
python2.5-dev
Abscissa07/22/07 06:35:17 (6 years ago)-
Message #178
you can also use {{{ }}}. Everything in between these will be displayed exactly how you type it.
nickishappy07/22/07 06:59:12 (6 years ago) -
Message #179
also, in Ubuntu are you having the button problems with the configuration that others seem to be having? I'm just curious. Ubuntu seems to be the only distro where people have problems with their buttons, and I just want to see if it's consistent at all.
If you need any more help setting things up, you know where to find us.
nickishappy07/22/07 07:01:29 (6 years ago)-
Message #180
I hate to throw a wrench in the debugging works, but the default mappings in acc_ptr and ir_ptr are working fine for me (Xubuntu 7.04/CWiid 6.00rc2). IIRC, it also worked fine a month or two ago when I was using Ubuntu 7.04/CWiid 5.03.
Could it be related to keyboard layout settings? Mine is set to the installation's default.
Another total shot in the dark, but my keyboard is a PS/2 rather than USB. I doubt that would make a difference, but maybe it does?
Abscissa07/22/07 08:44:19 (6 years ago) -
Message #181
Yea, like I thought, switching my mouse and keyboard from PS/2 to USB made no difference, so nevermind that.
Abscissa07/22/07 08:54:37 (6 years ago) -
Message #182
I did have one problem for awhile where I had to "sudo modprobe uinput" every time I rebooted, but I just figured out I could fix that by adding "uinput" to "/etc/modules".
The IR pointing is noticeably better in this version. I did see at least one oddity, though: Dragging a window around by the title bar seems to slow down the pointer's responsiveness. When you're doing that, it seems like there are "mouse move" events that are getting queued up faster than they're consumed. Not sure if that's really a CWiid issue though, for all I know it might be Xfce or something else.
Abscissa07/22/07 09:12:27 (6 years ago)-
Message #183
- The forums are wiki-interpreted - see WikiFormatting for details, but the simple answer is what nickishappy said.
- g++ is required? There's not a line of C++ in CWiid... Interesting.
- Do you have your window manager set to redraw the whole window as you drag it around? How does the lag compare to dragging a window around with the mouse?
- Thanks for noticing the IR pointer. I fear I put that off too long, dooming CWiid to forever be associated with bad IR tracking.
dsmith07/22/07 16:42:11 (6 years ago)-
Message #185
1. Thanks
2. g++ might not have been required, that was just one of a bunch of packages I grabbed (same with the auto* stuff, but I assume some of those were probably needed).
3. The window manager was redrawing the whole window while dragging (Didn't see a setting to turn that off, but I didn't really dig very far either). With a mouse, the cursor did track slower while dragging than while not dragging, but it didn't "feel" like it was lagging. Dragging a window did feel noticeably better with a mouse than the Wiimote.
Let me see if I can describe the mouse vs. wiimote dragging a little better. I'm going to completely make up all the numbers here, just for illustration. When moving the mouse cursor (non-dragging) with either the wiimote or mouse, the onscreen cursor's position moves, say, 5 pixels, every 10 milliseconds. When I'd drag a window with the mouse, the cursor's position only gets updated every, say, 40 milliseconds, but moves 20 pixels at a time. So it's still up-to-date with my movements, but a little jerky - like a game's framerate going from 30fps to 15fps. When I would drag a window with the wiimote, the cursor would still move every 40 milliseconds, but it would only move 5 pixels at a time, so all the "mouse moved" messages would get queued up and lag behind my actual physical movements. Kind of like trying to play an action game through MythTV (except that the lag would keep growing - well, maybe it didn't keep growing, it was hard to tell).
I'm not saying that's the actual phenomenon that was occurring, but that's just what it seemed like.
In any case, Xfce (or whatever it's called) was giving me problems with randomly-changing system font sizes (usually too small to read), so I ditched Xubuntu and did a fresh install of regular Ubuntu today. So I'll let everyone know how everything works out this time.
4. Yea, I would have been willing to help out with the IR myself, but I haven't had time. There were still two other IR problems I noticed, but I didn't mention because I figure it's still a WIP and you probably already knew. In fact I think I might have seen them mentioned on here before. But I may as well mention them here anyway, just for the record:
- The "roll" needs to be taken into account so X,Y movement is correct regardless of how the remote is tilted. (Either through the accelerometer or the orientation of the two IR dots. Not sure which would work better). ie, If the wiimote is rolled 90 degrees to the left, moving the wiimote right is moving the cursor down instead of right.
- When moving the cursor off the edges of the screen, I noticed it seems to be using some relative positioning calculations. (ie, using made-up numbers again, if you move the cursor to the exact left edge of the screen, point an inch further to the left, and then back an inch to the right, the cursor will have moved an "inch" inward from the edge of the screen, instead of staying on the edge.) The IR positions should be turned directly into absolute screen coordinates. Depending how X11 works, I assume you'd probably need to be able to query the screen's current resolution and the mouse's current position. I don't know enough about *nix GUIs ATM to know if that's a problem or not, though.
Abscissa07/23/07 03:36:33 (6 years ago) -
Message #186
Everything still working the same for me under Ubuntu as it did with Xubuntu. The window-dragging thing is mostly noticeable on things that are slow to redraw, like a terminal window set to show transparently through to the desktop.
Abscissa07/23/07 08:40:31 (6 years ago)
-
-
-
-
