Those bug threads actually make me *less* nervous. The first one explains that libjpeg-turbo is just a derivative of standard libjpeg that uses SIMD instructions to accelerate functionality by 2-4x. The second mentions that there have been improvements to libjpeg-turbo to make it ABI-compatible with libjpeg8.<br>
<br>Looking at the readme ( <a href="http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-turbo.txt">http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/trunk/README-turbo.txt</a> ) on the (still active) sourceforge project shows that by default it is API/ABI compatible with libjpeg v6b, which is what is currently most widely used. It can also be configured to be compatible with v7 or v8 instead, but there are a few v7+ features that are not supported.<br>
<br>-- <br>- Ben S.<br><br><div class="gmail_quote">On Tue, Jan 24, 2012 at 12:26 AM, Reinhard Tartler <span dir="ltr"><<a href="mailto:siretart@tauware.de">siretart@tauware.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Di, Jan 24, 2012 at 00:15:26 (CET), Mike Gabriel wrote:<br>
<br>
> Hi once again,<br>
><br>
> On Mo 23 Jan 2012 20:37:18 CET Mike Gabriel wrote:<br>
><br>
>> Hi again,<br>
>><br>
>> On Mo 23 Jan 2012 18:57:37 CET Mike Gabriel wrote:<br>
>><br>
>>>> Anybody try to configure for example ubutu to configure x2goserver<br>
>>>> to use libjpeg-tubro (<br>
>>>> <a href="http://sourceforge.net/projects/libjpeg-turbo/" target="_blank">http://sourceforge.net/projects/libjpeg-turbo/</a> ) instead libjpeg ?<br>
>>>> I have read that for example OpenNX client for neatx or freenx<br>
>>>> server recommend to use this because libjpeg-turbo have speed<br>
>>>> improvement than standard libjpeg and it will be use full to<br>
>>>> reduce transfer for x2go session. I don't know how to configure<br>
>>>> (or is it possible?) x2goserver on ubutu to use libjpeg-turbo<br>
>>>><br>
>>>> Regards<br>
>>><br>
>>> libjpeg-turbo support (from my perspective) is a distribution issue.<br>
>>> Libjpeg-turbo is pending for Debian sid inclusion:<br>
>>> <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341</a><br>
>>><br>
>>> As we do not have plans to ship libjpeg-turbo within the X2Go<br>
>>> repository currently, I guess we will have to wait for distro<br>
>>> inclusion in Debian/Ubuntu.<br>
>>><br>
>>> With other distros that already have libjpeg8 (optionally) replaced<br>
>>> by libjpeg-turbo, it should be possible to compile NX<br>
>>> (redistributed) against the faster libary.<br>
>>><br>
>>> There also is another NX related project on <a href="http://git.ethersoft.ru" target="_blank">git.ethersoft.ru</a> that<br>
>>> provides NX with libjpeg-turbo. However, that repos only builds NX<br>
>>> for FreeNX.<br>
>><br>
>> I have just tested an NX build against libjpeg-turbo. The<br>
>> libjpeg-turbo libraries I obtained from here:<br>
>> <a href="http://people.debian.org/%7Efabo/libjpeg-turbo_1.1.90+svn704-1/" target="_blank">http://people.debian.org/~fabo/libjpeg-turbo_1.1.90+svn704-1/</a><br>
>><br>
>> The test system was a Debian squeeze (so backporting from some brand<br>
>> new SID package is possible).<br>
>><br>
>> When using 16m-jpeg-9 compression over a UMTS (HDSPA) uplink the<br>
>> difference between libjpeg and libjpeg-turbo is smashing!!! It<br>
>> becomes so much smoother...<br>
>><br>
>> From my perspective, we should start testing on nx-libs with<br>
>> libjpeg-turbo in the nightly repository in the very very very near<br>
>> future.<br>
>><br>
>> The change-over is easy: if libjpeg-turbo62 is installable in the<br>
>> build chroot, NX builds against that one. If it is not present, it<br>
>> builds against libjpeg62.<br>
>><br>
>> @Developers: please give feedback on the proposed step.<br>
><br>
> Here is a recipe how to test NX with libjpeg-turbo:<br>
><br>
> ON SERVER<br>
> ---------<br>
> 1.<br>
> Install libjpeg-turbo from X2Go heuler repository (Debian-only)<br>
<br>
Won't that step replace the 'normal' system libjpeg? Are you sure that<br>
this step won't break existing applications?<br>
<br>
These bug threads make me a bit nervous:<br>
<br>
<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612341</a><br>
<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034" target="_blank">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602034</a><br>
<br>
<br>
Cheers,<br>
Reinhard<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Gruesse/greetings,<br>
Reinhard Tartler, KeyID 945348A4<br>
<br>
_______________________________________________<br>
X2go-Dev mailing list<br>
<a href="mailto:X2go-Dev@lists.berlios.de">X2go-Dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/x2go-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/x2go-dev</a><br>
</font></span></blockquote></div><br>