Hello,
> phodina writes:
>
> > Hi,
> >
> > recently I used Pulseview to debug eMMC issues.
> >
> > I was also surprised why they are some icons and others are missing.
> >
> > Based on the code some are implemented as png and some as svg.
> >
> > I tried to add the qtsvg-5 but it did not work an
Hi,
phodina writes:
> Hi,
>
> recently I used Pulseview to debug eMMC issues.
>
> I was also surprised why they are some icons and others are missing.
>
> Based on the code some are implemented as png and some as svg.
>
> I tried to add the qtsvg-5 but it did not work and made the resulting
> d
Theodoros Foradis writes:
> Ricardo Wurmus writes:
>
>> Theodoros Foradis writes:
>>
>>> My guess (not being familiar with qt), is that somehow, having the two
>>> inputs in different prefixes, causes the problem with the package's
>>> build system. I gave a look at the cmake files, but couldn't
Ricardo Wurmus writes:
> Theodoros Foradis writes:
>
>> My guess (not being familiar with qt), is that somehow, having the two
>> inputs in different prefixes, causes the problem with the package's
>> build system. I gave a look at the cmake files, but couldn't locate the
>> issue/fix.
>
> You c
Theodoros Foradis writes:
> My guess (not being familiar with qt), is that somehow, having the two
> inputs in different prefixes, causes the problem with the package's
> build system. I gave a look at the cmake files, but couldn't locate the
> issue/fix.
You could try to validate your hypothes
Hello,
commit b1e4c0fa514d94df9735685a037693e5c6efa5b2 changed the pulseview
package to build with modular qt.
Now, some icons do not appear at all in the gui. I had tried building
with modular qt before submitting the qt package, and this is why I
opted for "qt" as an input.
The two inputs from
