Discussion:
[capnproto] Shared Library Name
Schwarz, Eric
2017-10-03 17:02:14 UTC
Permalink
Hello Kenton,

would you mind changing the shared library name according to „standard“ naming convention (libcapnp-0.6.0.so => libcapnp.so.0.6.0)?
Otherwise, yes, at least Yocto will complain at build time and one needs to suppress the warning w/ „INSANE_SKIP = "dev-so"“.

Many thanks
Eric
________________________________
[Loading Image...] <http://100.arri.com/?utm_source=ARRI&utm_medium=email-footer&utm_campaign=E-Mail-Signature&utm_content=2017-09-Interactive-Timeline>

Get all the latest information from www.arri.com<http://www.arri.com/>, Facebook<https://www.facebook.com/TeamARRI>, Twitter<https://twitter.com/ARRIChannel>, Instagram<http://instagram.com/arri> and YouTube<http://www.youtube.com/user/ARRIChannel>.

Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRB 54477
Geschäftsführer: Franz Kraus; Dr. Jörg Pohlman; Stephan Schenk; Walter Trauninger
--
You received this message because you are subscribed to the Google Groups "Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+***@googlegroups.com.
Visit this group at https://groups.google.com/group/capnproto.
'Kenton Varda' via Cap'n Proto
2017-10-03 17:49:55 UTC
Permalink
Hi Eric,

The numbers that come after .so are not related to the library's marketing
version. They are instead an indication of ABI compatibility. Cap'n Proto
makes no attempt to be ABI-compatible between releases (because it is very
hard to do so in C++), hence we don't attempt to produce any ABI
compatibility indicator, but rather vary the whole library name. It would
be incorrect for us to move the version number to be after .so.

Cap'n Proto's approach is not unusual -- it's a normal, supported way of
using libtool. Why doesn't Yocto support it?

-Kenton
Post by Schwarz, Eric
Hello Kenton,
would you mind changing the shared library name according to „standard“
naming convention (libcapnp-0.6.0.so => libcapnp.so.0.6.0)?
Otherwise, yes, at least Yocto will complain at build time and one needs
to suppress the warning w/ „INSANE_SKIP = "dev-so"“.
Many thanks
Eric
________________________________
[http://www.arri.com/media/sign/2017_interactive-timeline_sign.jpg] <
http://100.arri.com/?utm_source=ARRI&utm_medium=email-
footer&utm_campaign=E-Mail-Signature&utm_content=2017-09-
Interactive-Timeline>
Get all the latest information from www.arri.com<http://www.arri.com/>,
Facebook<https://www.facebook.com/TeamARRI>, Twitter<https://twitter.com/
ARRIChannel>, Instagram<http://instagram.com/arri> and YouTube<
http://www.youtube.com/user/ARRIChannel>.
Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: MÃŒnchen - Registergericht: Amtsgericht MÃŒnchen -
Handelsregisternummer: HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: MÃŒnchen - Registergericht: Amtsgericht MÃŒnchen -
Handelsregisternummer: HRB 54477
GeschÀftsfÌhrer: Franz Kraus; Dr. Jörg Pohlman; Stephan Schenk; Walter
Trauninger
--
You received this message because you are subscribed to the Google Groups "Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+***@googlegroups.com.
Visit this group at https://groups.google.com/group/capnproto.
Loading...