Re: [Mike Frysinger] Re: [PATCH, V3 10/15] gdb: sim: buildsystem changes to accommodate libsframe

["Jose E. Marchesi" <jose.marchesi@oracle.com>]

>> But first things first: how do you people feel about libtoolizing the
>> rules in gdb/Makefile.in so GDB can handle the in-tree libtool libraries
>> in a more graceful way?
> What does "libtoolizing the rules" mean, in practice?

I would say to be able to refer to the libtool libraries (.la) directly
when linking, and let libtool do the magic of picking up the
corresponding archive or shared object.

This means that instead of the linker, you have to invoke something
like:

  libtool --mode=link foo.o bar.o baz.la ...

I have to confess I have never autotoolized a project that does not use
Automake.  Automake takes care of generating the right rules for linking
when you specify a .la library in either LIBADD or LDADD.

From the libtool manual:

  If you're not using Automake, and you don't know how to incorporate
  libtool into your package you need to do one of the following:

  1. Download the latest Automake distribution from your nearest GNU
     mirror, install it, and start using it.

  2. Learn how to write 'Makefile' rules by hand.  They're sometimes
     complex, but if you're clever enough to write rules for compiling
     your old libraries, then you should be able to figure out new rules
     for libtool libraries (hint: examine the 'Makefile.in' in the
     'tests/demo' subdirectory of the libtool distribution... note
     especially that it was automatically generated from the
     'Makefile.am' by Automake).