ament_export_interfaces assumes export name and target name are the same about ament_cmake HOT 2 CLOSED

Can't help but feel ament_export_interfaces is a somewhat confusing name for the method given the overloading of meaning with modern cmake's PUBLIC, PRIVATE, INTERFACE keywords.

from ament_cmake.

Have to admit, I didn't dig this far since I was only tickling the simplistic use case of one package, one library target, one export all glued together with ${PROJECT_NAME}.

Just managed to reproduce the problem.

# Dependency package 'abc'
add_library(${PROJECT_NAME} ${SOURCES})
install(TARGETS ${PROJECT_NAME} EXPORT foo_${PROJECT_NAME}
ament_export_interfaces(HAS_LIBRARY_TARGET foo_${PROJECT_NAME})

# Using package
message(FATAL_ERROR "${abc_INTERFACES}")

yields abc::foo_abc instead of the target abc::abc.

Do we need something like the following?

ament_export_interfaces(
   EXPORT foo_${PROJECT_NAME} targetA targetB targetC
   EXPORT bar_${PROJECT_NAME} targetD targetE targetF
)

then the targets here (not the export names) get gathered up in the xxx_INTERFACES variable for downstream packages.

from ament_cmake.