[
https://issues.apache.org/activemq/browse/AMQCPP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39207
]
Albert Strasheim commented on AMQCPP-115:
-----------------------------------------
Still trying to contact the ax_cflags_option author.
One more thing to think about with regards to DLLs and shared libraries: we
have some code in header files. Could this cause problems? Here I'm thinking
along the lines of some internal structure changing without affecting the
DLL/shared library "interface", but the user then has some AMQCPP code linked
into their executable that expects the old structure. If I have this right, one
should simply be able to upgrade the shared library in this case, without
requiring the user to recompile their program.
Meanwhile, I've been testing pyactivemq with the shared library on Linux and it
seems to work without problems.
> Change build to create dynamic libraries
> ----------------------------------------
>
> Key: AMQCPP-115
> URL: https://issues.apache.org/activemq/browse/AMQCPP-115
> Project: ActiveMQ C++ Client
> Issue Type: Task
> Environment: *nix, win32
> Reporter: Nathan Mittler
> Assignee: Nathan Mittler
> Priority: Minor
> Fix For: 2.1
>
> Attachments: amqcppdlldebug.diff, amqcppdllv1.diff, amqcppdllv2.diff,
> amqcppdllv3.diff, amqcppdllv4.diff, amqcpplibtoolv1.diff
>
>
> Based on a flurry of user requests, we need to add support for generating
> dynamic libraries to our automake scripts and the msvc project.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
