Am 30.01.2012 14:50, schrieb Mike Gabriel: > Hi Alex, > > On Mo 30 Jan 2012 14:01:02 CET Oleksandr Shneyder wrote: > >>> And your host should then run with libjpeg-turbo instead of libjpeg. >>> Please note, that this change affects every application on that system. >>> So... no warranty given from our side. Also, if testing libjpeg-turbo, >>> please read the documentation of libjpeg-turbo: >>> http://code.x2go.org/gitweb?p=libjpeg-turbo.git;a=blob;f=README-turbo.txt;h=ac37556f1335b006e6d15f3341290aa4b18dc8a6;hb=b72411e1b5aa2c0549be406284b90e9de407154c >>> >> >> It should be possible to use libjpeg-turbo only with nxproxy and >> x2goagent. If you specifying the directory where this libraries are >> installed in proxy and agent wrappers using the LD_LIBRARY_PATH >> environment variable. In that case it will not have affect on other >> applications in system. > > The fundamental question is if we want to offer libjpeg-turbo with X2Go > for distros that do not have libjpeg-turbo. If so, we could install > libjpeg-turbo into /usr/lib/nx/. > > Shall we do this? > > Mike
Hm, I'm not sure. I think, the users should be able to decide it. But we can make configuration of X2Go with libjpeg-turbo be easier. For example, if user have already installed libjpeg-turbo_1.1.90_i386.deb from http://sourceforge.net/projects/libjpeg-turbo/files/1.1.90%20%281.2beta1%29/ , agent wrapper can check if directory /opt/libjpeg-turbo/lib/ exists and export it to LD_LIBRARY_PATH. I'm not sure that we should provide libjpeg-turbo by ourself. regards, Alex -- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team email: [email protected] web: www.obviously-nice.de --> X2go - everywhere@home
signature.asc
Description: OpenPGP digital signature
_______________________________________________ X2Go-Dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
