On Fri, 2022-11-18 at 15:05 +0100, Bjørn Forsman wrote:
>
> I'm a maintainer of PulseView in Nixpkgs
> (https://github.com/nixos/nixpkgs) and I wonder if there are any plans
> for a new release soon?
I'm not aware of maintainers' plans, and I don't speak for the
project (and don't pretend to). So I cannot answer that question,
and won't attempt to, to not cause confusion.
But am afraid that just an application's release is not enough,
since it might also involve several libraries' releases. There
could be a tail of dependencies involved that you need to remain
aware of ...
> Rationale: the last release is about 2 years old, and it doesn't
> support qt-5.15, so currently we have to pin an old qt version (5.14)
> to keep pulseview "alive".
You can also put it the other way around. The Qt 5.15 library
no longer supports the API which earlier minor versions used to
have. But that's nitpicking, and doesn't solve your issue. Just
something that I have observed especially in the vicinity of C++
using projects, and that has been bothering me several times.
> For the record, here's a snippet of the build failure:
>
> /build/pulseview-0.4.2/pv/util.cpp:178:20: error: no match for
> 'operator<<' (operand types are 'QTextStream' and '<unresolved
> overloaded function type>')
> 178 | ts << forcesign;
> | ~~~^~~~~~~~~~~~
In that specific case, you could for example
$ git log -p --stat -S forcesign
and end up with commit ae726b70a7ad, the top of which addresses
the "ts << forcesign" phrase.
One alternative to bumping application code to a recent version
could be to backport some portability improvements. Got a list of
those portability issues, or a log that you can share? Maybe
others can lookup how they were addressed in unreleased versions
of mainline, and can help you unbreak your build again?
The other alternative could be to not wait for another release,
but just use recent master (while noting down the specific
version that you are using of course). sigrok master typically is
rather stable and usable, hiccups are rare.
PS: Do not bother me with private messages just because you
somehow got to lookup my address. Stick with public channels,
where others can join and help, and also can benefit from
information that was given. Thank you.
And if public channels with many more participants cannot get
you an answer, then I'm as unable to help you in private. Such
a request would only eat into my personal resources yet help
nobody. I'd rather spend this time on something more useful.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
