[
https://issues.apache.org/activemq/browse/AMQCPP-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39208
]
Timothy Bish commented on AMQCPP-115:
-------------------------------------
Inline functions should be fine with the caveat that if they change between
versions the user might have issues. For now the important this is getting it
to work. As far as I know, CMS has no code in the API headers, so in actuality
the use shouldn't really be affected by this to much. The main issue is
assuring that you have a shared heap without that you can't do anything with
this lib as it returns strings and such, which as you've seen will crash the
app as their internal char* data is allocated on one heap and freed on another,
not good.
One of the things that I was starting to look at as I was creating the decaf
lib was to pull out the code from the headers, more for ease of the user
looking at the headers, but you can't take it all out, template classes for
example. I haven't run into any issues yet on platforms like Linux with code
in headers. I'm sure that there will be some sort of issue with them on the
DLL nothing ever seems to work right with DLLs.
> 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.
