Compiling ==> 'GHOST_NDOFManagerX11.cpp' intern/ghost/intern/GHOST_NDOFManagerX11.cpp:30:19: error: spnav.h: No such file or directory Compiling ==> 'GHOST_ModifierKeys.cpp' intern/ghost/intern/GHOST_NDOFManagerX11.cpp: In constructor ‘GHOST_NDOFManagerX11::GHOST_NDOFManagerX11(GHOST_System&)’: intern/ghost/intern/GHOST_NDOFManagerX11.cpp:41: error: ‘spnav_open’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp: In destructor ‘virtual GHOST_NDOFManagerX11::~GHOST_NDOFManagerX11()’: intern/ghost/intern/GHOST_NDOFManagerX11.cpp:70: error: ‘spnav_close’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp: In member function ‘bool GHOST_NDOFManagerX11::processEvents()’: intern/ghost/intern/GHOST_NDOFManagerX11.cpp:83: error: ‘spnav_event’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp:83: error: expected ‘;’ before ‘e’ intern/ghost/intern/GHOST_NDOFManagerX11.cpp:84: error: ‘e’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp:84: error: ‘spnav_poll_event’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp:86: error: ‘SPNAV_EVENT_MOTION’ was not declared in this scope intern/ghost/intern/GHOST_NDOFManagerX11.cpp:96: error: ‘SPNAV_EVENT_BUTTON’ was not declared in this scope scons: *** [/var/tmp/portage/media-gfx/blender-2.60a/work/build/linux/intern/ghost/intern/GHOST_NDOFManagerX11.o] Error 1 scons: building terminated because of errors.
I will package mask 2.60a until this is fixed. I hope this is in Luca's interest, too.
(In reply to comment #1) > I will package mask 2.60a until this is fixed. I hope this is in Luca's > interest, too. Done.
+ 13 Nov 2011; Sebastian Pipping <sping@gentoo.org> blender-2.60a.ebuild: + Disable 3D mouse (as libspnav is not packaged yet) to fix compilation (bug + #390427) + To be concrete: + # libspnav not yet packaged (bug #390427) + echo 'WITH_BF_3DMOUSE=0' >> "${S}"/user-config.py + I'd unmask it now if there wasn't bug #390439, too.
As I mention on this comment: https://bugs.gentoo.org/show_bug.cgi?id=369599#c22 libspnav ebuild is in my overlay if you like to test it.
(In reply to comment #3) > I'd unmask it now if there wasn't bug #390439, too. Fixed, mask removed.
(In reply to comment #4) > As I mention on this comment: > https://bugs.gentoo.org/show_bug.cgi?id=369599#c22 > > libspnav ebuild is in my overlay if you like to test it. Found it at <http://git.overlays.gentoo.org/gitweb/?p=user/aluco.git;a=tree;f=app-misc/libspnav;hb=HEAD>. A few comments: - libspnav 0.2.2 does not seem to be licensed under GPL-3. Please fix the license information. - CFLAGS and LDFLAGS are not used in the build system correctly. The custom configure script could be a good starting point. - Configure has a switch for X11 support. The ebuild needs to touch it one way or another. - Your ebuild patches the Makefile. The patch looks good to me. Please check if upstream is willing to accept it and report about progress on that here. - If I'm not mistaken, an EAPI of 4 disallows us to stabilize this ebuild anytime soon. Please migrate to EAPI 3 or teach me better :-) - I am wondering how funcitonal the library alone is. Is the deamon or anything else needed to get spacenav hardware to work?
- app-misc feels wrong to me as a category. Please find something more suitable.
(In reply to comment #6) > (In reply to comment #4) > > As I mention on this comment: > > https://bugs.gentoo.org/show_bug.cgi?id=369599#c22 > > > > libspnav ebuild is in my overlay if you like to test it. > > Found it at > <http://git.overlays.gentoo.org/gitweb/?p=user/aluco.git;a=tree;f=app-misc/libspnav;hb=HEAD>. > A few comments: > > - libspnav 0.2.2 does not seem to be licensed under GPL-3. > Please fix the license information. OK, Fixed. > > - CFLAGS and LDFLAGS are not used in the build system correctly. > The custom configure script could be a good starting point. OK, Fixed with a new patch. > > - Configure has a switch for X11 support. The ebuild needs to > touch it one way or another. OK, Fixed. > > - Your ebuild patches the Makefile. The patch looks good to me. > Please check if upstream is willing to accept it and report > about progress on that here. OK, send on the spacenav-devel list with the new patch above. > > - If I'm not mistaken, an EAPI of 4 disallows us to stabilize > this ebuild anytime soon. Please migrate to EAPI 3 or teach > me better :-) I don't know but anyway libspnav probably won't be stabilize before blender because it's its only rev-dependency and blender has an EAPI of 4 too. I think they must both use the same EAPI. should blender migrate to EAPI 3 too ? > > - I am wondering how funcitonal the library alone is. Is the deamon > or anything else needed to get spacenav hardware to work? Your right, libspnav needs spacenavd deamon (on top of the HID driver, in userspace). I work on it. > > - app-misc feels wrong to me as a category. > Please find something more suitable. media-libs is better ? Modifications are in my overlay.
(In reply to comment #8) > (In reply to comment #6) > > (In reply to comment #4) > > > > - Your ebuild patches the Makefile. The patch looks good to me. > > Please check if upstream is willing to accept it and report > > about progress on that here. > OK, send on the spacenav-devel list with the new patch above. And accepted : http://sourceforge.net/mailarchive/message.php?msg_id=28442809 > > > > > - I am wondering how funcitonal the library alone is. Is the deamon > > or anything else needed to get spacenav hardware to work? > Your right, libspnav needs spacenavd deamon (on top of the HID driver, > in userspace). I work on it. spacenavd is in my overlay with some patches nearly identical to libspnav, then I send them too to the spacenav-devel list.
Anthoine, out of curiosity: do you have access to spacenav hardware to quick-test this with? I thought it would be nice to know the software is actually working, not just compiling. Just thinking.
(In reply to comment #10) > Anthoine, out of curiosity: do you have access to spacenav hardware to > quick-test this with? I thought it would be nice to know the software is > actually working, not just compiling. Just thinking. No, I haven't. You're right compiling in not enough. Ebuilds are ready until I get one or someone else tests them.
(In reply to comment #11) > No, I haven't. You're right compiling in not enough. Ebuilds are ready until I > get one or someone else tests them. Thanks for your quick reply. What do you think about asking for owners of such devices on Gentoo media, e.g. the gentoo-user mailing list? Whom would you want to write the text for it? Alternatively, any idea how easy the hardware is to get and what numbers we are talking?
(In reply to comment #12) > Thanks for your quick reply. What do you think about asking for owners of such > devices on Gentoo media, e.g. the gentoo-user mailing list? Whom would you > want to write the text for it? Alternatively, any idea how easy the hardware > is to get and what numbers we are talking? I didn't think that I can send a mail on gentoo-user to get test. I can write a mail tomorrow. There are 4 different 3Dconnexion devices that must works with libspnav from one hundred dollars to 4 hundred : http://www.3dconnexion.com/buy/shop.html
+ 06 Feb 2012; Sebastian Pipping <sping@gentoo.org> blender-2.60a.ebuild, + metadata.xml: + Introduce support for 3D mouse based on dev-libs/libspnav (bug #390427), + co-operation with Anthoine Bourgeois +