Yop, On Mon, Jul 30, 2012 at 2:55 PM, Vincent Torri <[email protected]> wrote: > I plan to update mupdf from 0.9 to 1.0. So i'm writing the build > system for that version. As mupdf is not necessarly included in the > distros, I integrate the mupdf source in eyesight and I build it. I'm > now wondering if I should build a shared lib of mupdf and install it, > or if i should statically link mupdf against the pdf module of > eyesight. Basically: > > 1) integrate mupdf and its thirdparty package (which includes : > libjpeg, freetype, openjpeg, jbig2dec and zlib), i build them and I > statically link all that against the pdf module of eyesight > 2) or I ask the user to have libjpeg, freetype, openjpeg, jbig2dec and > zlib already installed, I build mupdf and I link mupdf statically > against the pdf module of eyesight > 3) or I ask the user to have libjpeg, freetype, openjpeg, jbig2dec and > zlib already installed, I build mupdf as a shared lib and the pdf > module will use the shared lib of mupdf. > > What is the best solution ?
I think 2 will be better as it doesn't conflict at all with the distribution without getting insane and building 10 dependencies inside. -- Cedric BAIL ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
