[Scons-dev] Tutorial for Linux versioned libraries

[Gary Oberbrunner]

SCons Install just copies files (and in this case makes symlinks).
Building installers is a whole different thing.  SCons can do it, but
Install isn't what you're looking for.

On Tue, May 19, 2015 at 8:51 AM, anatoly techtonik <techtonik at gmail.com>
wrote:

> On Tue, May 19, 2015 at 3:29 AM, William Blevins <wblevins001 at gmail.com>
> wrote:
> >> Anatoly,
> >>
> >> > I've sent a pull request with the changes:
> >> > https://github.com/techtonik/RHVoice/pull/1
> >>
> >> Thanks. I need to understand the issue better before merging it.
> >> 1. If RHVoice needs those version numbers at all?
> >> 2. Why it tries to load so.0 when there is .0.0.0?
> >
> >
> > Here is my understanding of linux standards for shared libraries:
> >
> > Example:
> > thing.so -> thing.so.1
> > thing.so.1 -> thing.so.1.2.3
> > thing.so.1.2.3 (the real file)
> >
> > GNU linkers (and others) embed shared library information into the final
> > product in the form thing.so.1, so that the library can undergo patch
> > updates (EG. 1.2.3 -> 1.2.4) without requiring the application to be
> > recompiled.
>
> That make it clear. Thanks.
>
> The only question is the Install stuff. The operating system knows better
> where to install things, no? It creates a package registry and tracks all
> the
> files. Is SCons Install just a development hack?
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>



-- 
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150519/3f8c422e/attachment.html>