[ANN] opentrack 2.0 beta 1 released!
-
Hi folks,
I’m happy to announce the availability of a new opentrack git build for Ubuntu 18.04 based 64bit systems. You can download it here:
https://zif.gplrank.info/hoover/opentrack/opentrack-git-20190118.tar.gz
MD5 checksum:
fdb2a6ae0d13750310c340ca62a4378d opentrack-git-20190118.tar.gz
The tar archive extracts to /opt/opentrack-git-20190118 as usual.
All the best & have a good weekend,
Uwe
-
Hey,
Please install libevdev-dev and libeigen3-dev before configuring with cmake. Otherwise you’re missing several modules.
I’m attaching an AppVeyor config for building on a clean Ubuntu 18.04 environment. It’s notably missing “software-properties-common” and “curl” since AppVeyor VMs have it in already. You should be able to automate the build based on that.
-
Thanks Stanislaw!
Both packages are installed automatically by my openstack user init script during spin-up of the VM before attempting the opentrack build:
ii libeigen3-dev 3.3.4-4 all lightweight C++ template library for linear algebra ii libevdev2:amd64 1.5.8+dfsg-1 amd64 wrapper library for evdev devices
I hope these are the correct versions.
All the best, Uwe
-
You specifically need libevdev-dev in order for the virtual joystick output module to be built.
-
Hi,
I added the package to the cloudinit script and rebuilt opentrack, should be in the download package now as well.
All the best,
Uwe
-
Sorry to necromance this thread, but has anyone built the current version of opentrack (git or 2.3.12) successfully on an Ubuntu 20.04 based platform?
TIA & all the best,
Uwe
-
Sorry to necromance this thread, but has anyone built the current version of opentrack (git or 2.3.12) successfully on an Ubuntu 20.04 based platform?
TIA & all the best,
Uwe
i built a deb package for my debian testing, you find it in the github page of the project.
-
Thanks for the info massima, however I seem to be too dumb to find it in the various subfolders… can you enlighten me to just where you uploaded it? Or should I be looking for a spec file that allows me to build the package from source on a debian based system like Ubuntu?
Thanks & all the best,
Uwe
-
Never mind, I managed (after lots of teeth gnashing and hair pulling) to re-compile the latest git sources on Linux (Mint 20) with the barest minimum of plugins, protocols and filters that I’m using (pointtracker, accelera, wine, xplane).
I’ll prepare a new Linux download over the next couple of weeks that’s compatible with Ubuntu 20.04, and I’m happy to report the xplane11 / Linux side of things is already working quite well.
All the best,
Uwe
PS: The worst issue was that I have apparently deleted my old cloudinit script for Ubuntu 18.04 which spun up a VM in an openstack cluster, installed all the needed packages, pulled the git source and xp11 sdk from the net and more or less automatically build the latest opentrack… I have no idea how this could have happened :uham:
-
Thanks for the info massima, however I seem to be too dumb to find it in the various subfolders… can you enlighten me to just where you uploaded it? Or should I be looking for a spec file that allows me to build the package from source on a debian based system like Ubuntu?
Thanks & all the best,
Uwe
I uploaded it in my gdrive space (here), it can be reached by a link in the wiki page of the project.
The deb package can be installed via “dpkg -i opentrack_2.3.12-1_amd64.deb”, via gdebi or other tools; if you use latest Ubuntu, you shouldn’t have dependency issues. I compiled the core code without Wine/aruco/etc. -
Hi folks,
here’s a current build of opentrack for Ubuntu 20.04 based Linux systems. It contains just the minimum stuff to get head-tracking working (I’m using the DelanClip with a ps/eye webcam, so nothing fancy), but I hope some folks may find it useful still:
o input plugins: pointracker, test, UDP over network
o output protocols: libevdev, udp, flightgear, wine,
o filters: Accelera
https://www.magentacloud.de/lnk/jwBpmS02 (26MB)
Installation: extract to your /opt/ directory as “root” (for write permissions):
sudo tar -C /opt -xvpf opentrack_ubuntu_20_04.tar.gz
Alternatively, use the archive manager of your choice to extract the contents.
All the best & happy holidays!
Uwe
-
Could anyone help me a litlle with opentrack build? I’m trying to make fedora package. So far I’ve made to a point where opentrack compiles and runs, but offers only pointtrack input and accela filter. No other inputs/filters and no output protocols are offered.
List of dependencies installed:
git-2.29.2
cmake-3.18.4
qt5-qttools-5.15.2
qt5-qttools-devel-5.15.2
qt5-qtbase-5.15.2
qt5-qtbase-devel-5.15.2
qt5-qtbase-private-devel-5.15.2-2
procps-ng-3.3.16
procps-ng-devel-3.3.16
opencv-4.3.0
opencv-devel-4.3.0
libevdev-1.11
libevdev-devel-1.11
wine-6.3
wine-devel-6.3 -
I’ll try to come up with a list of packages I needed for my 20.04 build, I think I took some notes when I finally managed to get a working binary including the wine protocol… (as I pointed out elsewhere my build also only includes pointtracker, accelara and the wine protocol so it works with xp11 on Linux and BMS under WINE.
Cheers, Uwe
-
BTW, are you sure cmake is picking up all the required packages? I remember having to edit some sdk paths in some cmake ini and / or using the cmake curses interface.
While I admire the ability to create cross platform builds using a single source tree, for someone coming from the usual “configure; make ; make install” crowd the cmake stuff can be overwhelming at first (to say the least).
1061 sudo apt install c++
1062 sudo apt install cpluscplus
1065 sudo apt install g++
1067 sudo apt install qt5
1079 sudo apt install qtchooser
1083 apt install libqt5gui5
1084 apt install libqt5gui5-dev
1085 apt install libqt5gui5
1086 apt install libqt5| grep dev
1092 sudo apt install qt5make
1093 sudo apt install qmake
1095 sudo apt install qt5-qmake
1099 apt install qt5ct
1101 sudo apt install qt5base-dev
1105 sudo apt install qtdeclarative5-dev
1108 sudo apt install qt5-qmltooling-plugins
1110 sudo apt install qttools5-dev
1113 sudo apt install libeigen3-dev
1116 sudo apt install libprocps-dev
1126 sudo apt install libtf2-eigen-dev
1143 sudo apt install libopencv-videoio-dev
1146 sudo apt install libopencv-dev
1201 sudo apt install qtbase5-private-dev
1282 sudo apt install clang
1341 sudo apt install libwine-development-dev
1343 sudo apt install libwine32-development-dev
1465 apt install gcc9-multilib
1466 apt install gcc-9-multilib
1473 sudo apt install wine32-development-tools:i386
1699 apt install winehq-developmentAlso I think I had to check out some source stuff using git (eigen3 or similar), basically it was a lot of groping around in the dark before I got opentrack to build with the stuff I require on my system.
I’ll try to dig deeper and report back here.
Cheers, Uwe
-
Thanks a lot Hoover, my install missed eigen3-devel, opencv and opencv-devel packages, everything else seem to be in palce already.
However cmake didn’t found eigen3 dir, i’ve pointed it to /usr/share/cmake/eigen3/ where all the cmake eigen3 files are located.
Yet new build still won’t offer anything else than pointtrack tracker and accela filterOnce list of build and runtime dependences will be complete, it need to be pushed to opentrack wiki, so many ppl have issues with doing a proper build.
-
Is your WINE development stuff located correctly by ccmake? Did you download the flightgear SDK stuff and point ccmake to it? Do you have the wine32 bit / cross compile stuff installed?
I’ve never understood the logic behind running
cmake .
in the opentrack source directory, apparently that’s how you can manually set your paths to the various packages correctly in a curses-based interface and then cmake heads off once you hit “g” for generate and pulls all the dependencies together.
I bet sthalik is laughing his head off somewhere at my poor attempts to make sense of cmake, but hey, I’m just a poor Unix guy with two and a half decades of sysadmin experience, so how should I be able to make heads or tails of cmake?
All the best,
Uwe
-
building opentrack is kinda black magic, I’ve found opensuse package, so I’ve downloaded src.rpm, and after few package names adjustments used its spec file to build fedora rpm.
Opentrack from new build package worked the same as build from source, ie no output protos, no extra filters nor trackers.
So just to make sure i installed tumbleweed on vm, dowloaded opentrack rpm for suse and installed it in vm. Guess what, it works here as designed, with all the filters, trackers and protocols it was build
I found few differences comparing ldd of opentrack-api lib on fedora i suse.
Suse lib used 3 extra libs- libcap
- double-conversion
- libselinux
So i’ve installed devel packages for those libs and rebuilded opentrack package. Unfortunatelly it didn’t help My investigation gonna continue tommorow.
-
Hi xeno,
you need to run
ccmake .
in opentrack’s source directory to change all the pathnames to the devel packages, stuff you checked out from git and so on. I’m still unclear on whether you’ve run “ccmake .” or not
If you look in the top level source dir, there’s a file called [email protected] or similar (from memory, not at my gaming machine right now) where I built the tar package, I think this is a text file that’s generated when you hit “g” in “ccmake” to generate the build files.
I could really kick myself for not saving that cloudinit script I wrote for Ubuntu 18.04 back in the day which would spin up a clean 18.04 VM in openstack, install all the dependencies and the cmake version required to build opentrack, checkout opentrack source via git, build a tar file from the compiled binaries and then upload them somewhere for distribution. It wasn’t as much work as it sounds but naturally some critical info was lost together with this script which I’m now apparently unable to piece together anymore.
I checked my bash history on the gaming machine yesterday and there’s a ton of “ccmake .” and “ccmake …” (probably run in the build directory), but nothing concise that I could present here as a one-stop solution. Apparently I also moved quite a few plugins out of the source directory for which I had no need, but at least the wine related stuff would be built that you require for BMS and xplane11.
I’ll look further into this but tbh cmake positively scares me to bits so maybe I was so happy I got my stuff to compile finally that I ran away and forgot all about it… it was Christmas after all
All the best,
Uwe
-
I’ve did all the dance with cmake … ccmake . and so on. These sdk-paths files are either generated by some other mean or created by hand, i’ve did ccmake, it complains about missing user config file (sdk-paths-<user>@<compiler>-<os>.cmake) made and generate configuration, but new sdk-paths file wasnt generated in the build, nor source dit. My guess is, It has to be something with Fedora doing some stupid things, because I did try to use suse spec file to build rpm. Opentrack installed from fedora rpm behave the same as build from source. But opentrack in suse installed from rpm build from same spec file works just fine, albeit is missing pointtrack tracker and wine output.</os></compiler></user>
-
Here’s my (partly redacted) build script for ubuntu 18.04 that I just discovered in some deep backup folder
#!/bin/bash
LOG=“/var/tmp/ubu.ci.log”
today=$(date +%Y%m%d)echo “Cloudinit run started @
date
.” >> $LOGPREFIX=/opt/opentrack-git-“$today”
echo “Install prefix: $PREFIX” >> $LOGecho “Adding i386 arch….” >> $LOG
dpkg --add-architecture i386echo “Adding WineHQ repos (needed for wine-development stuff)” >> $LOG
wget -qO- https://dl.winehq.org/wine-builds/Release.key | sudo apt-key add -
apt-add-repository ‘deb http://dl.winehq.org/wine-builds/ubuntu/ bionic main’
apt-get updateapt -y –install-recommends install build-essential emacs-nox libprocps-dev unzip libc6-dev-i386 libqt5serialport5-dev libqt5webkit5-dev qttools5-dev libopencv-dev htop apt-file libeigen3-dev lib32stdc+±7-dev libevdev-dev >> $LOG
echo “Installing WINE packages…:” >> $LOG
apt -y install fonts-wine libwine:i386 libwine-dev:i386 libwine-development:i386 libwine-development-dev:i386 wine-devel-i386:i386 wine-development:i386 wine-stable:i386 wine-stable-dev:i386 wine-stable-i386:i386 wine32-development:i386 wine32-development-tools:i386 >> $LOG
echo “Removing 64bit WINE packages…” >> $LOG
apt -y remove wine64-development wine64-tools libwine-development:amd64 >> $LOGupdate file cache
apt-file update >> $LOG
echo “installing cmake” >> $LOG
(wget -O - https://cmake.org/files/v3.12/cmake-3.12.4-Linux-x86_64.tar.gz | tar -C /usr/local -xpzf -) >> $LOG
ln -s /usr/local/cmake-3.12.4-Linux-x86_64 /usr/local/cmake
echo ‘export PATH=/usr/local/cmake/bin:$PATH’ >> /etc/bash.bashrcSet our own PATH so we can use cmake later on
export PATH=/usr/local/cmake/bin:$PATH
echo “cloning opentrack git repo” >> $LOG
mkdir /usr/local/src
cd /usr/local/src
git clone https://github.com/opentrack/opentrack.git
echo “Setting src ownership…” >> $LOGecho “Setting up x-plane 11 SDK…” >>$LOG
cd /var/tmp
wget http://developer.x-plane.com/wp-content/plugins/code-sample-generation/sample_templates/XPSDK301.zip
unzip XPSDK301.zip
mv SDK /usr/local/xplane_sdk
chown -R ubuntu /usr/local/xplane_sdkecho “Preparing CMake Cache…”
mkdir /usr/local/src/opentrack/build/
cat < <eof>/usr/local/src/opentrack/build/CMakeCache.txt
CMAKE_BUILD_TYPE:STRING=RELEASE
//Wine install prefix
SDK_WINE_PREFIX:PATH=/usr
//Path to X-Plane SDK
SDK_XPLANE:PATH=/usr/local/xplane_sdk
EOF
echo CMAKE_INSTALL_PREFIX:PATH=$PREFIX >> /usr/local/src/opentrack/build/CMakeCache.txtchown -R ubuntu /usr/local/src
echo “Adding hostname…” >> $LOG
echo “127.0.0.1 test-opentrack” >> /etc/hostsecho “attempting opentrack build…
date
” >> $LOGcd /usr/local/src/opentrack/build
/usr/local/cmake/bin/cmake … >> $LOG
make -j2 >> $LOG
make install >> $LOG
chown -R ubuntu … $PREFIXecho “opentrack build run finished
date
” >> $LOGecho “Cloudinit run finished @
date
.” >> $LOG</eof>