[
https://issues.apache.org/jira/browse/QPID-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529355#comment-13529355
]
Andrew Stitcher commented on QPID-4499:
---------------------------------------
I disagree with Gordon.
Generating bindings is a client development activity in my view. With the .i
files exported in this way developing bindings is no longer restricted to those
with access to the qpid tree, but the only requirement to develop a new client
binding is the client include files.
This strong decoupling is a very good thing from my point of view.
Obviously you wouldn't export .i files that relate to individual bindings to
the include files, but the .i that give the general typemaps that are useful
for every binding and point at all the necessary include files seem like very
good candidates for export to me.
> Relocate all Swig .i files to include directories.
> --------------------------------------------------
>
> Key: QPID-4499
> URL: https://issues.apache.org/jira/browse/QPID-4499
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Client
> Reporter: Darryl L. Pierce
> Assignee: Darryl L. Pierce
> Fix For: 0.20
>
>
> Since these files are used for client development, they need to be shipped.
> Additionally, since swig defaults to looking in the standard include file
> directories, they should be placed in the same place as other qpid include
> files; i.e., /usr/include/qpid/ on *nix platforms.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
