Open GoogleCodeExporter opened 9 years ago
Let me know if you want the full strace, as the above is only half of it.
Pretty short, but guessing you might have a better idea what's going on from
this point.
Original comment by rogerx....@gmail.com
on 23 Oct 2013 at 4:48
Apparently from searching the Internet forums, I first need to run ltr_gui to
create a config file required by ltr_pipe.
However I'm missing ltr_gui due to a compiler error, for which was buried
within the compiler stdout and did not terminate the build on error.
So likely two issues here? 1) The compile (makefile) didn't break and
continued after the error. And 2) A missing dependency check
dev-libs/mini-xml! (ie. =dev-libs/mini-xml-2.7-r1 works here for resolving the
dependency.)
QT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 -I.
-I.. -I. -I.. -I/usr/X11R6/include -I. -I. -o extractor.o extractor.cpp
gcc -c -pipe -Wall -Wextra -DLTR_GUI -I
/home/roger/src/linuxtrack/linuxtrack-install/include -g -Wall -W -D_REENTRANT
-DQT_WEBKIT_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 -I.
-I.. -I. -I.. -I/usr/X11R6/include -I. -I. -o game_data.o game_data.c
game_data.c:4:18: fatal error: mxml.h: No such file or directory
compilation terminated.
make[4]: *** [game_data.o] Error 1
make[4]: Leaving directory
`/home/roger/src/linuxtrack/linux-track-read-only.mine/src/qt_gui'
~/src/linuxtrack/linux-track-read-only.mine/src
Original comment by rogerx....@gmail.com
on 23 Oct 2013 at 5:10
Mark this as solved & fixed once the configure script is augmented to check for
this dep. I've gotten ltr_gui and extracted the firmware. I just hope the
ltr_gui process spawned the wine process into a separate bottle, and am
guessing from the QT GUI prompt it passed a switch to simply unpack and not
install, although the process did proceed through the steps of the usual
TrackIR_5.2.2.Final.exe install under Windows.
Also not mentioned within the documentation (ie. man ltr_pipe), users first use
ltr_gui to extract the firmwares required for their TrackIR device which also
requires a run time dependency of wine (which I can easily check within build
scripts but would be nice to see mention within the man file), and then need to
use ltr_gui to create a configuration file. From here, a simple ltr_pipe can
be spawned.
I must say, I'm otherwise mildly impressed. ;-)
(Next step, working with flightgear.)
Original comment by rogerx....@gmail.com
on 23 Oct 2013 at 5:24
Hello,
I will go over the configure.ac and friends to make sure all the dependencies
are found and used correctly. And documentation is on the list too.
The NP's package does go to its own bottle in /tmp, so it won't ruin any of
yours.
I managed to make the Flightgear run on my setup (although it does complain
about not being able to compile a pixel shader) and I'm going to try a new
protocol (no nasal script needed). I'll keep you posted once I have it working.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 23 Oct 2013 at 5:45
Original issue reported on code.google.com by
rogerx....@gmail.com
on 23 Oct 2013 at 4:46