qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jiri Daněk (JIRA) <j...@apache.org>
Subject [jira] [Commented] (PROTON-1638) Need to improve proton-c build tree layout
Date Fri, 20 Oct 2017 12:21:00 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212547#comment-16212547

Jiri Daněk commented on PROTON-1638:

Would you also consider adding header files to the build targets in CMake build files? This
is something that C++ IDEs (be it QT Creator, Kdevelop, or Clion) require to work properly.
[1], [2] If you aren't aware of any downsides of this, I'd like to try this after the repository
layout is changed, and if it works for me, propose a patch.

[1] https://github.com/sauter-hq/cmake-ide-support
[2] https://youtrack.jetbrains.com/issue/CPP-270

> Need to improve proton-c build tree layout
> ------------------------------------------
>                 Key: PROTON-1638
>                 URL: https://issues.apache.org/jira/browse/PROTON-1638
>             Project: Qpid Proton
>          Issue Type: Improvement
>    Affects Versions: proton-c-0.18.0
>            Reporter: Andrew Stitcher
> The proton-c tree layout is annoying in a number of ways:
> * Since the split with proton-j there is a superfluous top level
> * CMake build flags don't propagate properly because examples are not in the correct
> ** Examples should be in the binding subtree that they are examples
> ** Otherwise the information for a particular binding and its examples are split into
2 different parts of the proton-c tree.
> ** This means that the installation for a binding is split
> ** It is unatural in CMake to split build flags like this - CMake is hierarchical

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message