versioning C++ includes

[Nathan Myers]

On Tue, Jun 25, 2002 at 09:07:43PM +0200, Rainer Orth wrote:
> "B. Kosnik" <bkoz@nabi.net> writes:
> 
> > > I think the binary compatibility issues are incorporated in the
> > > installed .so (or .a) name -- existing practice.  As far as source
> > > code is concerned, it suffices to use the compiler release number. 
> > 
> > Yep. This is correct. Phil's symbol versioning bits implemented this for
> > libstdc++ 3.1.0 on systems that use GNU ld, have shared libgcc, etc.
> 
> And even without this interface versioning support, proper use of 
> libtool's -set-version gives you proper binary compatibility.  
> ... So please avoid
> duplicating this functionality with subdirs of $libdir or some such:
> this is both unnecessary and gives you nightmares on platforms that
> don't hardcode rpath into binaries/libraries.

Of course --rpath semantics are unsatisfactory, but saying so doesn't 
help solve the problem.

Besides that, my libtool-1.4.2 doesn't have a -set-version option,
and I don't see anything like it mentioned in the changelog for
the unstable version 1.4d.  Did you have some other option in mind?

I don't think libtool can help much with the problem I described.

Nathan Myers
ncm at cantrip dot org