On Mon, Dec 8, 2008 at 5:32 AM, Vadim Lebedev <[EMAIL PROTECTED]> wrote:
> I'be a suggestion though that you use not RC2 but the latest revision, we
> did a lot of stabilisation work, and we're going to release RC3 today or
> tommorrow after fixing a small Mac quirck
That's good news! I will sure move top RC3.
(btw: the two carsh reports have been done using the tip)
> Btw we're going to integreate almost all of your patches too.
Thanks!
On Mon, Dec 8, 2008 at 11:08 AM, Vadim Lebedev <[EMAIL PROTECTED]> wrote:
> I've reviewed your patches and i wonder why did you changed coredumper to
> static mode build?
That's actually a good question. I did not remember and I reached the
folllowing conclusion:
-the path comes from the wengophone 2.1 package, I am quite sure it
was made because of RPATH issue
-I included it in the qutecom package because I had an error during
installation that it could not find the libcoredumper.so library, so I
thought the patch was still needed
-however coredumper seems not be used any longer! I think it has been
replaced by googlebreakpad. So the only useful part f that patch is
just removing the copying of libcoredumper.so during (make install);
coredumper itself maight me removed from the source tree (or is it
still used in some cases?)
Btw: most of the .so libraries are just loaded as startup, and are
just private to qutecom:
libphapi.so => /usr/lib/qutecom/libphapi.so (0x00007ff7bbe1f000)
libwebcam.so => /usr/lib/qutecom/libwebcam.so (0x00007ff7bbbfb000)
libowutil.so => /usr/lib/qutecom/libowutil.so (0x00007ff7bb9d2000)
libphapiutil.so => /usr/lib/qutecom/libphapiutil.so (0x00007ff7bb7ce000)
libowsl.so => /usr/lib/qutecom/libowsl.so (0x00007ff7bab00000)
liblibpurple.so => /usr/lib/qutecom/liblibpurple.so (0x00007ff7b9724000)
libowbase.so => /usr/lib/qutecom/libowbase.so (0x00007ff7b8a3e000)
libpsiidle.so => /usr/lib/qutecom/libpsiidle.so (0x00007ff7b883a000)
So why not building them statically into the executable?
Having them as shared library has no benefit and just slows down the
startup, I think.
Thanks,
Ludovico
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev
