Menu

#64 Wrong filename of the library

None
open
nobody
None
5
2014-11-27
2014-11-27
No

Hello,

When building the latest version of openobex, library is called libopenobex.so.1.7.1 and the symlink pointing it is called libopenobex.so.2

This is IMHO not correct.

According to the following link, the library should be called libopenobex.so.2.x.x:
https://www.sourceware.org/autobook/autobook/autobook_91.html

Related

Bugs: #64

Discussion

  • Laurent Bigonville

    More information can be also found at: http://pusling.com/blog/?p=352

     
    • Hendrik Sattler

      Hendrik Sattler - 2014-11-28

      Hi,

      you are mistaken. The .so.2 is the name for the ABI version 2. This can be related to the library version but it does not have to.

      The major version did not change to 2.x because the API did not change in a major way.

      The broken world of autotools is not an argument. They made up their own library numbering/naming scheme but that's just their point of view. I consider their methods limiting and wrong.

      HS

      Am 27. November 2014 23:31:49 MEZ, schrieb Laurent Bigonville bigon@users.sf.net:

      More information can be also found at: http://pusling.com/blog/?p=352


      [bugs:#64] Wrong filename of the library

      Status: open
      Group: None
      Created: Thu Nov 27, 2014 08:21 PM UTC by Laurent Bigonville
      Last Updated: Thu Nov 27, 2014 08:21 PM UTC
      Owner: nobody

      Hello,

      When building the latest version of openobex, library is called
      libopenobex.so.1.7.1 and the symlink pointing it is called
      libopenobex.so.2

      This is IMHO not correct.

      According to the following link, the library should be called
      libopenobex.so.2.x.x:
      https://www.sourceware.org/autobook/autobook/autobook_91.html


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/openobex/bugs/64/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #64


Log in to post a comment.