Il 07/11/2013 15:23, Liang Guo ha scritto:
It is a problem of libjpeg-turbo, libjpeg-turbo was in debian for a
shot time, then be renamed to libturbojpeg1 and cannot be linked with
-ljpeg, so I disabled libjpeg-turbo in spice.
I tried to build with the jpegturbo but failed for missed header
Il 07/11/2013 15:23, Liang Guo ha scritto:
It is a problem of libjpeg-turbo, libjpeg-turbo was in debian for a
shot time, then be renamed to libturbojpeg1 and cannot be linked with
-ljpeg, so I disabled libjpeg-turbo in spice.
I have not noticed that spice can work on arm, if it do, I'll try
It is a problem of libjpeg-turbo, libjpeg-turbo was in debian for a
shot time, then be renamed to libturbojpeg1 and cannot be linked with
-ljpeg, so I disabled libjpeg-turbo in spice.
I have not noticed that spice can work on arm, if it do, I'll try to
build it on *all* architecture.
Thanks,
Source: spice
Severity: normal
Hi, I see on repository that spice packages was switched to libjpeg-turbo but
after was returned to libjpeg, why?
The jpeg-turbo FWIK have only performance increase using SIMD instructions (MMX
and SSE) on x86 and NEON instructions on arm.
The use of jpeg-turbo pro
4 matches
Mail list logo