[
https://issues.apache.org/jira/browse/QPID-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403893#comment-13403893
]
Steve Huston commented on QPID-4096:
------------------------------------
Thanks for responding, Cliff. I don't intend for WCF/Interop or qpidxarm or
qpidclient to be placed in a static library - they would all remain DLLs.
However, the Boost bits would be included instead of existing in a DLL. It just
alleviates the need to manage Boost versions when moving Qpid out of the
development environment.
Would that be a problem for CLR or MSDTC?
> Change WCF to link static with Boost
> ------------------------------------
>
> Key: QPID-4096
> URL: https://issues.apache.org/jira/browse/QPID-4096
> Project: Qpid
> Issue Type: Improvement
> Components: WCF/C++ Client
> Affects Versions: 0.17
> Environment: Windows
> Reporter: Steve Huston
> Priority: Minor
>
> Currently both C++ and WCF/C++ Interop build with linking Boost dynamically.
> This requires the Boost DLLs to be present at run time.
> The C++ client build can change to link Boost statically in the cmake
> configuration step. This removes the need to have the Boost DLLs available at
> run time, with the possible increase in linked qpid dll size.
> The WCF/C++ Interop project is not based on Cmake, so it has no such setting.
> I'd like to change the WCF/C++ Interop to link statically with Boost to
> remove the need to have Boost available at run time.
> This change would make packaging easier, as it would remove the need to
> package Boost DLLs with Qpid or require a specific Boost version/options to
> be installed on the target system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
