Skip to content
This repository was archived by the owner on Apr 19, 2022. It is now read-only.

qt5base: Build config change for PyQt5#683

Draft
ar664 wants to merge 2 commits intotermux:masterfrom
ar664:feature-qtsemaphore
Draft

qt5base: Build config change for PyQt5#683
ar664 wants to merge 2 commits intotermux:masterfrom
ar664:feature-qtsemaphore

Conversation

@ar664
Copy link
Copy Markdown
Contributor

@ar664 ar664 commented Mar 23, 2022

In regards to my issue termux/termux-packages#10104 . I'm still trying to get PyQt5 to build on termux.

@ar664 ar664 force-pushed the feature-qtsemaphore branch from 8ef0743 to 9d3d1bf Compare March 23, 2022 17:58
@ar664
Copy link
Copy Markdown
Contributor Author

ar664 commented Mar 23, 2022

@xtkoba Is it possible to choose which architecture I want to build in the workflow? I'm just working on aarch64 right now, in this draft.

@xtkoba
Copy link
Copy Markdown
Contributor

xtkoba commented Mar 23, 2022

CI runs for all 4 architectures. But you can temporarily set TERMUX_PKG_BLACKLISTED_ARCHES:

TERMUX_PKG_BLACKLISTED_ARCHES="arm, i686, x86_64"

CI for an excluded arch normally finishes in 3 to 4 minutes.

@xtkoba
Copy link
Copy Markdown
Contributor

xtkoba commented Mar 28, 2022

I see the following lines in $PREFIX/include/QtCore/qtcore-config.h of the artifact:

#define QT_FEATURE_sharedmemory -1
#define QT_NO_SHAREDMEMORY

and

#define QT_FEATURE_systemsemaphore -1
#define QT_NO_SYSTEMSEMAPHORE

I doubt if this PR improves the situation for termux/termux-packages#10104.

I have enabled these features in qt5-qtbase version 5.15.3-1. Please rebase if any further changes are needed.

I also doubt if -system-proxies improves anything with respect to exported symbols.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants