Here are some new ebuilds for sigrok.
There might be some dependencies that I'm lacking, and otherwise, I think I need to edit the sigrok-qt ebuild compile() stage to just call qmake then make (or inherit something from qt).
Otherwise, they work... can't say that sigrok works particularly well yet though. I didn't find either UI particularly usable (at least with my USBee AX).
Oh well, just thought I would put them in the hands of developers.
I'll probably try to migrate some work I've done on the syscomp-design hardware so that it can be used as a logic analyzer as well.
Created attachment 318136 [details]
This is the open source firmware ebuild. It pulls in sdcc to build the firmware.
Created attachment 318138 [details]
this ebuild requires
in its files/ directory
Created attachment 318140 [details, diff]
patch that accompanies fx2lib-9999.ebuild
Created attachment 318142 [details, diff]
patch that accompanies fx2lib-9999.ebuild
Created attachment 318144 [details]
Created attachment 318146 [details]
Created attachment 318148 [details]
Created attachment 318150 [details]
Created attachment 318152 [details]
Created attachment 318154 [details]
this ebuild still needs some qt-love ... any volunteers familiar with qt ebuilds?
Created attachment 318156 [details]
a wrapper that will install sigrok-gtk, sigrok-qt, or both
... might still need some love
I just stuck these under the dev-embedded category, but feel free to put them elsewhere.
Hi, thanks for the ebuilds. Emerging them right now. Some notes:
- sigrok-gtk misses dependencies (libsigrok and evetually libsigrokdecode and libsigrokfile)
- IMHO, it's better to use SLOT-dependencies for libusb in libsigrok (and better depend on virtual/libusb than on dev-libs/libusb) and for python:3 in libsigrokdecode
- The sigrok-qt ebuild needs to depend on (at least) qt-gui. But I'll try that one later and attach an updated version here that uses the "qt4-r2" eclass. Wouldn't be my first qt4-r2-based ebuild
one more note: I needed to add:
inherit eutils autotools
to the libsigrokfile-ebuild, otherwise it failed with:
/usr/lib64/portage/bin/isolated-functions.sh: line 213: wait: `Failed Running automake !': not a pid or valid job spec
It doesn't fail when I uninstall automake:1.12 but that ain't the right solution :)
libsigrokdecode didn't need this modification
fx2lafw fails to compile here: make: *** [fx2.lib] Segmentation fault
I don't know if it's temporary (we're talking about live-git ebuilds here) or not. Will retry in some days. So here's where the story ends for today ...
Created attachment 328366 [details]
Ebuild for sigrok-qt using the qt4-r2 eclass and no autotools at all :)
(In reply to comment #15)
> Created attachment 328366 [details]
> Ebuild for sigrok-qt using the qt4-r2 eclass and no autotools at all :)
No autotools at all can sometimes be a good thing :)
I've created new ebuilds in an overlay avalaible here: https://github.com/jmesmon/sigrok-overlay
This adds non-live ebuilds, pulseview (the new qt gui), and drops libsigrokfile, sigrok-qt, sigrok-gtk, and fx2lib (fx2lafw includes a modified version).
i've added libserialport now:
i've added libsigrok now:
it required a bit of work to get it to build cleanly though
i've added libsigrokdec now:
i've added sigrok-cli now:
Comment on attachment 318152 [details]
the qt interface is deprecated upstream, so won't bother adding ebuilds for it
Comment on attachment 318154 [details]
the gtk interface is deprecated upstream, so won't bother adding ebuilds for it
Comment on attachment 318156 [details]
i don't see value in this meta package. no one installs the libs directly (unless they're a dev), and that leaves you with picking an interface -- either the CLI or the GUI. at which point this ebuild is overkill.
Comment on attachment 318148 [details]
libsigrokfile appears to be dead, so won't bother with ebuilds for it
i've added sigrok-firmware-fx2lafw now:
Comment on attachment 318136 [details]
afaict, these firmware ebuilds are no longer needed with sigrok-firmware-fx2lafw in the tree
and finally pulseview is in the tree:
this bug is plenty long now, and all the relevant packages are in the tree
if you run into troubles with any of them, let's move the work to new bugs
Thanks for getting it in!