cppAntiMicroX/antimicrox #98Not a task: not reproduced

Remove antilib shared object because it's not really shared!

envgap__AntiMicroX__antimicrox-98

Original GitHub issue ↗Dated source checkout ↗Opened 2020-11-29

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit: 8e35365c41c84ddc166a1ab7916af67b2fc6be14
Manifest: CMakeLists.txt
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

AntiMicroX/antimicrox #98 · read the original issue

Original Issue:

> I was browsing the file list of the built package. We are building all c++ stuff under `libantilib.so.1` and linking `libantilib.so` to it.

>

> That looks a little dumb. If it won't cause problems, we could name it `libantimicro(x).so` and no `.1` file for more cleanness?

>

> edit: numbers in the shared object name ending is for versioning the file and letting different programs link against different object versions. Since we are shipping the appropriate object with every version and we are the only program using it, it defeats the purpose.



And @gombosg said:

> Libraries have to have soname fields. If we don't need it because it's not shared, then let's not ship a shared library.



So we should seek to completely remove it and statically link our code.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]