Re: Compiling problems

[Owen Taylor <otaylor redhat com>]

Dan Kegel <dank@kegel.com> writes:

> Owen Taylor wrote:
> > 
> > Dan Kegel <dank@kegel.com> writes:
> > > pkg-config is the spawn of the devil because it makes
> > > it difficult to cross-compile ...
> > 
> >  * With pkg-config, lookup of compilation information is standardized,
> >    so cross compilation can be handled in a standard way. Maybe some
> >    feature addition to pkg-config is needed, but *fixing* the problem
> >    is possible.
> > 
> >  * With package-specific config scripts every package is different.
> > 
> >  * With old fashioned hardcoded autoconf tests, it's hell for everyone.
> > 
> > Please don't confuse:
> > 
> >  - I have trouble getting stuff to cross compile with pkg-config right now
> > 
> > With:
> > 
> >  - pkg-config is the wrong way to do things
> 
> If I sounded grumpy, it's because I'm tired of fixing people's code
> so it is cross-compile-friendly.  
> pkg-config looked like One More Thing to Fix.  It still kinda does.  
> I rather prefer autoconf macros for each library; they're more powerful.
> One way pkg-config, and indeed configure scripts, fall down is that
> they are inflexible when it comes to tailoring which shared libraries
> you link to.  This means you have to link to all of the shared libraries
> a package provides, even if you only use a few of them.  This shouldn't
> be a problem, except that simply linking to a shared library seems
> to pull it into memory, causing RAM waste that can be a killer on
> embedded systems.

 pkg-config --libs glib-2.0                  [ -lglib only ]
 pkg-config --libs gmodule-2.0               [ -lgmodule and -lglib because gmodule requires glib ]
 pkg-config --libs gobject-2.0 gthread-2.0   [ -lgobject -lgthread -lglib ]

Regards,
                                        Owen