Am 6. August 2018 22:29:21 MESZ schrieb Alexander Neundorf :
>On 2018 M08 6, Mon 21:54:33 CEST Hendrik Sattler wrote:
>> Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof
>:
>> >Hello everyone,
>> >
>> >I noticed that it sometimes happens that I find a package for a
>shared
>> >object
Alexander Neundorf wrote:
> On Mon, 2018-08-06 at 21:54 +0200, Hendrik Sattler wrote:
> > Is there ANY reason to use libtool library versioning? It might
> > surprise people but it really is not any kind of standard.
> >
> > Just change the SOVERSION when you make incompatible ABI changes
> >
On 2018 M08 6, Mon 21:54:33 CEST Hendrik Sattler wrote:
> Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof
:
> >Hello everyone,
> >
> >I noticed that it sometimes happens that I find a package for a shared
> >object file(s) (or DLLs, on platforms like Windows) that have a build
> >set up
On Mon, 2018-08-06 at 21:54 +0200, Hendrik Sattler wrote:
Hello Hendrik,
> > https://github.com/pvanhoof/dir-examples/tree/master/cmake-example
> >
> > The idea is that the examples are as correct as possible. That
> > means the examples should simple and educational. Easing (some
> > amount)
Am 6. August 2018 20:27:23 MESZ schrieb Philip Van Hoof :
>Hello everyone,
>
>I noticed that it sometimes happens that I find a package for a shared
>object file(s) (or DLLs, on platforms like Windows) that have a build
>set up using cmake, that doesn't set everything that should be set.
>
Hello everyone,
I noticed that it sometimes happens that I find a package for a shared
object file(s) (or DLLs, on platforms like Windows) that have a build
set up using cmake, that doesn't set everything that should be set.
Usually as packagers of various popular open source softwares correct
