[texworks] compiling texworks with static poppler and hunspell
Jonathan Kew
jfkthame at googlemail.com
Thu Jun 4 20:10:31 CEST 2009
On 4 Jun 2009, at 18:59, Norbert Preining wrote:
> On Do, 04 Jun 2009, Jonathan Kew wrote:
>>> is there a way to compile texworks on Unix with static poppler,
>>> libpoppler-qt4, and hunspell?
>>
>> And presumably static QtCore, QtGui, QtXml. This should be possible -
>> it is a recognized and documented approach to deploying Qt apps. See
>> http://doc.qtsoftware.com/4.5/deployment-x11.html ..
>
> Nice hint. I have now compiled a version for x86_64 with static qt and
> poppler and I got the following remaining deps (hunspell .a lib is
> missing, this is a bug in the debian packages):
> $ ldd texworks
> linux-vdso.so.1 => (0x00007fffe54b1000)
> libhunspell-1.2.so.0 => /usr/lib/libhunspell-1.2.so.0
> (0x00007f89f0121000)
> libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f89efee2000)
> libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f89efc5b000)
> libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0
> (0x00007f89efa16000)
> libSM.so.6 => /usr/lib/libSM.so.6 (0x00007f89ef80e000)
> libICE.so.6 => /usr/lib/libICE.so.6 (0x00007f89ef5f3000)
> libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f89ef3ea000)
> libfontconfig.so.1 => /usr/lib/libfontconfig.so.1
> (0x00007f89ef1b9000)
> libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f89eefa8000)
> libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f89eec6d000)
> libz.so.1 => /usr/lib/libz.so.1 (0x00007f89eea56000)
> libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0
> (0x00007f89ee852000)
> librt.so.1 => /lib/librt.so.1 (0x00007f89ee64a000)
> libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f89ee386000)
> libdl.so.2 => /lib/libdl.so.2 (0x00007f89ee182000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x00007f89edf67000)
> libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f89edc58000)
> libm.so.6 => /lib/libm.so.6 (0x00007f89ed9d5000)
> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f89ed7ba000)
> libc.so.6 => /lib/libc.so.6 (0x00007f89ed467000)
> libpcre.so.3 => /usr/lib/libpcre.so.3 (0x00007f89ed238000)
> libuuid.so.1 => /lib/libuuid.so.1 (0x00007f89ed034000)
> libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f89ece0b000)
> libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f89ecc09000)
> libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f89ec9ed000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f89f0363000)
> libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f89ec7e8000)
>
> But I don't think that we win a lot with that, since we still have
> deps
> on glib, gconf, gobject (coming from libQtCore.a!), so we will have a
> hard time to get rid of all the stuff ... buaahhhh.
I guess the question is whether it's reasonable to assume that things
like glib, gconf, gobject, etc are "standard" on a modern graphical
desktop system. Presumably it would be possible to build Qt with only
static versions of these available(?) and then you wouldn't end up
with these dependencies, but I have no idea whether it's really
worthwhile.
Of course it's possible to set up a Linux system that doesn't include
many of these libs -- you could have a text-only system without even
X11 -- but we don't care about that as a platform for texworks. At
least I don't. :)
JK
More information about the texworks
mailing list