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

ASF subversion and git services commented on PROTON-2494:
---------------------------------------------------------

Commit 6bded7019cc31fd699b1d53d378a4ec76bcdb689 in qpid-proton's branch 
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=6bded701 ]

PROTON-2526/PROTON-2494: Remove final uses of distutils in Python setup

Also significantly simplify the setup logic by using the CMake build to
generate the SWIG c file and don't do it at Python setup time at all.


> Improve python-qpid-proton wheel build regarding pkgconfig and deps
> -------------------------------------------------------------------
>
>                 Key: PROTON-2494
>                 URL: https://issues.apache.org/jira/browse/PROTON-2494
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: build, python-binding
>    Affects Versions: proton-c-0.36.0
>            Reporter: Jiri Daněk
>            Assignee: Andrew Stitcher
>            Priority: Major
>             Fix For: proton-c-future
>
>
> https://github.com/apache/qpid-proton/pull/356#pullrequestreview-872590821
> {quote}
> I can see inconsistency between openssl and cyrus sasl libs. We don't seem to 
> use pkgconfig for cyrus sasl in the same way as for openssl. ~And in fact we 
> seem to have to work around not using pkg-config when we are on windows in a 
> strange way!
> Also we include some (copied in) code to interface to pkgconfig, but there 
> seems to be a good pypi package - pkgconfig which does this stuff and is 
> geared up for use in setup.py too. Maybe we should be using this rather than 
> the strange homegrown thing we've got?
> {quote}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to