| Products > Test Equipment |
| Open source lxi-tools and liblxi v1.0 released for GNU/Linux |
| << < (16/67) > >> |
| lundmar:
--- Quote from: 3hristian on November 25, 2017, 08:59:35 am ---Howdy, I keep running into issues with LXI-TOOLS... so far support from Lundar has been great. Jet spamming GitHub with issues that might only be my system isn't too great. I have been following install instructions on this forum jet I got stuck here: after installing LIB, and TOOLS trying to start the program on the command line. --- Code: ---$ lxi --help lxi: error while loading shared libraries: liblxi.so.1: cannot open shared object file: No such file or directory --- End code --- i am running --- Code: ---Linux LAB 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux --- End code --- Or --- Code: ---Linux Mint 18.1 Cinnamon 64-bit --- End code --- if that floats your goat. As solving this issue has many solutions hence I wanted to ask first before fumbling around. --- End quote --- Hi 3hristian, No worries, you just keep spamming github as much as you like - that is what is what the issue tracker is for ;) I'm sorry about your installation issue - luckily it's a temporary situation. I'm working on getting lxi-tools/liblxi into Debian so that they will eventually be included in distributions like Ubuntu and Mint. This way users don't have to bother with the challenges of manual installation. Currently software packages are being updated for Fedora. I hope to find a lxi-tools/liblxi maintainer for Debian soon. Assuming you followed the git install instructions in the top of this thread to the letter then you shouldn't run into any issues with lxi-tools not finding liblxi. However, the issue you see can be bypassed by using for example this command: --- Code: ---$ LD_LIBRARY_PATH=$HOME/opt/lxi/lib ./lxi --version v1.12 --- End code --- Or by simply exporting the variable like so and running the lxi tool: --- Code: ---$ export LD_LIBRARY_PATH=$HOME/opt/lxi/lib $ lxi --version lxi v1.12 --- End code --- Assuming your install location is $HOME/opt/lxi as suggested in the git install instructions. |
| lundmar:
I realize that many people are not comfortable building and installing stuff from source. Unfortunately it takes quite some effort and time to find package maintainers for the various distributions and even then there is usually a large turnaround time to update packages :( To try bypass these issues I've created a snap for lxi-tools. This means that it is now possible to install the latest release version of lxi-tools on the most popular distributions like so: --- Code: ---$ snap install lxi-tools --- End code --- The great thing about snaps is that I maintain the snap directly and when I update my lxi-tools snap it will be immediately available for users to install. No delay! :-+ It's pretty cool, check it out. I've tested it on Fedora 27 and Ubuntu 17.10 but it should work on various other distributions too (Mint, ArchLinux, Debian, Gentoo, OpenSuse, Manjaro, etc.). See https://snapcraft.io for how to install snap on your distribution. P.s.: There is one minor issue though: after installing the lxi-tools snap the tool command is 'lxi-tools.lxi' and not 'lxi'. Will be fixed later. P.p.s: lxi-tools snap details can be seen here: https://dashboard.snapcraft.io/dev/snaps/8744 |
| nctnico:
--- Quote from: lundmar on November 26, 2017, 03:40:10 am ---I realize that many people are not comfortable building and installing stuff from source. Unfortunately it takes quite some effort and time to find package maintainers for the various distributions and even then there is usually a large turnaround time to update packages :( --- End quote --- The easy way around that is to pack everything (including libraries) into a distribution independant package like firefox does. A statically linked binary should work well too. |
| lundmar:
--- Quote from: nctnico on November 26, 2017, 12:28:59 pm --- --- Quote from: lundmar on November 26, 2017, 03:40:10 am ---I realize that many people are not comfortable building and installing stuff from source. Unfortunately it takes quite some effort and time to find package maintainers for the various distributions and even then there is usually a large turnaround time to update packages :( --- End quote --- The easy way around that is to pack everything (including libraries) into a distribution independant package like firefox does. A statically linked binary should work well too. --- End quote --- That is true. However, there are some advantages to the snap solution because it actually includes and runs lxi-tools inside its own containerized Ubuntu core image runtime that runs specific versions of dynamic services like e.g. avahi that lxi-tools rely on for mDNS/DNS-SD discovery. If I do a static it is likely that the avahi dbus interface protocol will not work on various distributions because of version differences of their avahi daemon. Also, it's a big plus for end users that they can use the simple snap install command to manage their lxi-tools package and when I push updates they will have a super easy way to upgrade ('snap refresh lxi-tools'). In the end, that is simpler than messing with and setting up a static tarball that might or might not work. The snap support will only improve and spread to more distributions so for application distribution this is the future and I'm jumping right in he he. Once I get the last details of my lxi-tools snap sorted out it will be perfect. |
| lundmar:
FYI - it is now possible to install latest development version using snap: --- Code: ---$ snap install lxi-tools --edge --- End code --- The lxi-tools snap from the edge channel automatically follows the latest git version via automatic CI using https://build.snapcraft.io Also, the lxi-tools snap is now built for the following architectures: amd64, i386, armhf For those interested, here is the snapcraft configuration for the lxi-tools snap: https://github.com/lxi/lxi-tools.snapcraft |
| Navigation |
| Message Index |
| Next page |
| Previous page |