> Most likely this is Autotools issue. At least older autoconf
> checked the existence of X libraries by checking for libXt
> and it added that also to the linker line.
>
> However, none of the modern (Gtk, Qt) UI toolkits use libXt
> nor require it. Only something obsolete like Motif needs it.
> Does your program really use/require libXt?
Could be, but specifically in my case, mozilla does depend on them (for rendering stuff), and the checking at configure time is also a bit complex. So the dependecy is no at build time only but also at run-time. Anyways , I intend to ask on a mozilla mailing list about how hard would be removing such dependency ?
The problem is the "AC_PATH_XTRA()" configure test. It defines the
X_PRE_LIBS variable, which - from the documentation - contains
libraries, which must be linked before you link the "regular" X11
libraries. The configure scripts for at least debian and maemo
distributions returns "-lSM -lICE" for this variable. Configure scripts
which try to be correct and portable and thus use this variable will
automatically link against this libraries - even if they do not use
them. I removed the use of X_PRE_LIBS temporary to avoid linking this
libraries.
Note also that recent versions of Xorg offer pkg-cocnfig *.pc files for
the various X11 files. I plan to use them if available and fall back to
AC_PATH_XTRA if not. These *.pc files do not show above behaviour of
automatically adding -lSM and -lICE.
I do not have any problem with libXt.
still wordering why are these libraries available on devel rootstrap (so it makes possible to your app to depend on them) but not on the device image ?
--
--Antonio Gomes
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
