You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is extremely inconvenient for cross-platforms users, and against of the intention of CMake config to abstract from implementation details. (And I do not refer to the fact that static library linkage adds a -static suffix.)
I suggest to standardize on sbml for both package and target basename.
If there is a desire to add a lib prefix to MSVC import or runtime libraries, this can be achieved e.g. by adjusting the OUTPUT_NAME target property.
Alternatively, standardize on libsbml if there is also sbml tool.
Maybe this opportunity could be used to add an sbml:: namespace prefix to the exported target names,
and to move the sbml-target into the sbml cmake package, too.
The text was updated successfully, but these errors were encountered:
The installed CMake config package and target names vary depending on platform. On windows, users need:
but on other platforms, it is:
This is extremely inconvenient for cross-platforms users, and against of the intention of CMake config to abstract from implementation details. (And I do not refer to the fact that static library linkage adds a
-static
suffix.)I suggest to standardize on
sbml
for both package and target basename.If there is a desire to add a
lib
prefix to MSVC import or runtime libraries, this can be achieved e.g. by adjusting theOUTPUT_NAME
target property.Alternatively, standardize on
libsbml
if there is alsosbml
tool.Maybe this opportunity could be used to add an
sbml::
namespace prefix to the exported target names,and to move the
sbml-target
into thesbml
cmake package, too.The text was updated successfully, but these errors were encountered: