This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Embedded
- :
- FlexNet Embedded Knowledge Base
- :
- Why do FNE archives use 'versioned' shared object files on Linux?
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Why do FNE archives use 'versioned' shared object files on Linux?
Why do FNE archives use 'versioned' shared object files on Linux?
Summary
Why do FNE archives use 'versioned' shared object files on Linux?Question
We're running our setup on a x64 bit SuSE 11.3 system using the flexnet_client-xt-c-x64_linux-2017.08.0.tgz toolkit. When we link the libFlxClientXT_pic.a and libFlxCommonXT_pic.a archives with our build, the resulting executable requires that we include the versioned files libFlxComm64.so.2017.08 and libFlxCore64.so.2017.08. Is there a reason these 'versioned' shared object files are required rather than just using libFlxCo*64.so files?Answer
FlexNet Embedded aligned with standard Linux procedures as of the 2016 R2 release.Here's some more info on how they are used:
https://unix.stackexchange.com/questions/475/how-do-so-shared-object-numbers-work
No ratings