Using a more specific library name

[S-Dafarra]

No description provided.

[S-Dafarra]

Actualy, this broke the export on windows. If I look at trintrinTargets.cmake I see

add_library(trintrin::trintrin_msgs SHARED IMPORTED)

while I was expecting

add_library(trintrin::msgs SHARED IMPORTED)

In fact, the test is failing

[traversaro]

ALIAS targets are not installed, so I guess this is expected. If you want to keep the exported target name to be trintrin::msgs and not trintrin::trintrin_msgs, we need to keep the target name to be msgs, and change the output name to be trintrin_msgs to avoid ambiguous file names on the file system. Having said that, I do not understand ho Linux and macOS tests are passing.

[traversaro]

Having said that, I do not understand ho Linux and macOS tests are passing.

Mistery solved, the Install and test installed package check is done only on Windows.

[traversaro]

we need to keep the target name to be msgs, and change the output name to be trintrin_msgs to avoid ambiguous file names on the file system

Basically this means changing back most of the changes in this PR, and add instead:

set_target_properties(msgs PROPERTIES OUTPUT_NAME trintrin_msgs)

[S-Dafarra]

Thanks a lot @traversaro, that fixed the issue. Merging and releasing

[traversaro]

@S-Dafarra can we bump the version to 0.1.0 instead of 0.0.2 ? A change in the library name is a ABI breaking change.

[S-Dafarra]

@S-Dafarra can we bump the version to 0.1.0 instead of 0.0.2 ? A change in the library name is a ABI breaking change.

Sure! I opened #7