activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Strasheim (JIRA)" <>
Subject [jira] Commented: (AMQCPP-22) Use common name for ActiveMQ C++ library on Windows and Linux
Date Thu, 14 Dec 2006 23:46:02 GMT
    [ ] 
Albert Strasheim commented on AMQCPP-22:

The convention on Windows seems to be to leave off the lib- prefix. In build tools like SCons
(and many others), calling a library 'foo' means 'foo.lib' on Windows and 'libfoo.a' on Linux.

> Use common name for ActiveMQ C++ library on Windows and Linux
> -------------------------------------------------------------
>                 Key: AMQCPP-22
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Timothy Bish
>             Fix For: 1.1
> We're using SCons to build our application that links against the ActiveMQ-CPP library
on Windows and Linux.
> The Visual Studio files included with ActiveMQ-CPP builds a library called "activemq.lib"
whereas the Linux Autotools build builds a library called "libactivemq-cpp.a". SCons takes
care of the platform-specific prefix (lib or nothing) and the suffix (.a or .lib), but the
base names of the library still differs, i.e. activemq vs activemq-cpp.
> I think it would make sense to standardise on one library name across all platforms.
Personally, I'd go for "activemq", but "activemq-cpp" is fine, as long as it's the same everywhere.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message