2008-04-01 15:35:03     gmime, glib2 and their many dependencies

2008-04-01 15:35:03     gmime, glib2 and their many dependencies

Doug Bailey (UNITED STATES)

Message: 53484    I have an application that needs to link to the gmime library.  Gmime  in turn has a number of dependencies. 

As far as I can tell, I need to bring in:

gmime

glib2

gettext

libiconv

All these packages are scaring me in that I may be eating up memory resources.

Am I over doing this or is there a way that much of this functionality can be built into uclibc or some other package?

Thanks for any help,

Doug Bailey

QuoteReplyEditDelete

2008-04-03 02:29:39     Re: gmime, glib2 and their many dependencies

Yi Li (CHINA)

Message: 53582    Firstly I think you may configure the libraries to build only the necessary part, so the library size could be smaller.

Also it is worth to try to build the library and see the real size.

But it is an issue for non-mmu system, that shared library cannot be partly mapped and loaded into memory.

QuoteReplyEditDelete

2008-04-03 14:10:45     Re: gmime, glib2 and their many dependencies

Mike Frysinger (UNITED STATES)

Message: 53614    if we assume uClibc has fully functional support equivalent to what glibc has (and this assumption isnt valid), then that would only cover gettext and libiconv.  any other library you get from gnome.org (so glib / gmime / pango / atk / etc...) would still all have to be external.  and i dont think you can build anything nowadays from the gnome project without those core libraries.

QuoteReplyEditDelete

2008-04-04 19:21:27     Re: gmime, glib2 and their many dependencies

Mike Frysinger (UNITED STATES)

Message: 53660    if you want shared libraries, you use FDPIC ELF, not FLAT.  if you use FLAT, then you'll be getting static archives only.

(yes, you can do a shared libraries with share flat, but the method is hackish, time consuming, and generally not worth it)