Template Repository Question

Template Repository Question

[Pyle, Mike]

Please excuse me if this is obvious but I'm trying to get a handle on how
the template repositories work. I understand that the .rpo files are built
and at link time collect2 investigates them and recompiles and relinks as
necessary to instantiate all the required templates. But how, if at all, can
this work for any libraries that you might be including that use templates?
Are you stuck making the libraries explicitly instantiate any templates that
are used? It seems like this would be the case but any insights would
appreciated.

Template Repository Question

[Pyle, Mike]

Please excuse me if this is obvious but I'm trying to get a handle on how
the template repositories work. I understand that the .rpo files are built
and at link time collect2 investigates them and recompiles and relinks as
necessary to instantiate all the required templates. But how, if at all, can
this work for any libraries that you might be including that use templates?
Are you stuck making the libraries explicitly instantiate any templates that
are used? It seems like this would be the case but any insights would
appreciated.

Re: Template Repository Question

[Mike Stump]

> From: "Pyle, Mike" <mike.pyle@centraxcorp.com>
> To: egcs@egcs.cygnus.com
> Date: Tue, 2 Mar 1999 17:45:07 -0800 

> Please excuse me if this is obvious but I'm trying to get a handle
> on how the template repositories work. I understand that the .rpo
> files are built and at link time collect2 investigates them and
> recompiles and relinks as necessary to instantiate all the required
> templates. But how, if at all, can this work for any libraries that
> you might be including that use templates?  Are you stuck making the
> libraries explicitly instantiate any templates that are used? It
> seems like this would be the case but any insights would
> appreciated.

You have a mound of options.

You can decide where to put things explicitly by hand editing the rpo
files.  This should provide 100% control to the user. Certain power
users may not be happy with anything less.  I of course don't
recommand this.

You can do a full link with the library files, and let it fail, but in
the process, it will instantiate everything it can (someplace).

If you have multiple libraries, you can do them step wise, and get
ever increasing sets without any duplication:

gcc f1.o
ar f1.a f1.o
gcc f2.o f1.a
ar f2.a f2.o
...

You can not include any template instantiations, and require the user
#include <libtemplates.h> in a .c file, and compile it with -frepo and
ensure that everything the library needs _can_ be instantiate in that
file.

There are a host of other options of course that don't involve -frepo.

Re: Template Repository Question

[Mike Stump]

> From: "Pyle, Mike" <mike.pyle@centraxcorp.com>
> To: egcs@egcs.cygnus.com
> Date: Tue, 2 Mar 1999 17:45:07 -0800 

> Please excuse me if this is obvious but I'm trying to get a handle
> on how the template repositories work. I understand that the .rpo
> files are built and at link time collect2 investigates them and
> recompiles and relinks as necessary to instantiate all the required
> templates. But how, if at all, can this work for any libraries that
> you might be including that use templates?  Are you stuck making the
> libraries explicitly instantiate any templates that are used? It
> seems like this would be the case but any insights would
> appreciated.

You have a mound of options.

You can decide where to put things explicitly by hand editing the rpo
files.  This should provide 100% control to the user. Certain power
users may not be happy with anything less.  I of course don't
recommand this.

You can do a full link with the library files, and let it fail, but in
the process, it will instantiate everything it can (someplace).

If you have multiple libraries, you can do them step wise, and get
ever increasing sets without any duplication:

gcc f1.o
ar f1.a f1.o
gcc f2.o f1.a
ar f2.a f2.o
...

You can not include any template instantiations, and require the user
#include <libtemplates.h> in a .c file, and compile it with -frepo and
ensure that everything the library needs _can_ be instantiate in that
file.

There are a host of other options of course that don't involve -frepo.