Per-platofrm scopes in pyproject.toml

Patrick Stinson patrickkidd at gmail.com
Wed Oct 7 13:48:29 BST 2020


Roger that. It looks like I have to manually do a platform check and then add to the “sources” variable.

> On Oct 6, 2020, at 11:57 PM, Phil Thompson <phil at riverbankcomputing.com> wrote:
> 
> On 06/10/2020 22:28, Patrick Stinson wrote:
>> Aha. Yes, I thought I had seen something like this somewhere in the docs.
>> These examples are for sysroot components and don’t work when building
>> the plugins in dev using sip-build. It looks like this is somehow
>> handled with AbstractComponent.target_platform_name.
>> But how to do this when building the component in dev using sip-build,
>> i.e. prior to any use of pyqtdeploy?
> 
> You need to implement it in code in a project.py script.
> 
> Phil
> 
>>>> On Oct 6, 2020, at 12:31 PM, Phil Thompson <phil at riverbankcomputing.com> wrote:
>>> On 06/10/2020 19:09, Patrick Stinson wrote:
>>>> How does one specify which platform a setting is for in
>>>> pyproject.toml? I can’t find this in the sip docs or PRP 518 spec.
>>>> For example, I have a module source file that is only for Mac, and
>>>> another for windows, something like:
>>>> [win#tool.sip.bindings._pkdiagram]
>>>> sources = [ "unsafearea.cpp", "_pkdiagram.cpp", "_pkdiagram_win32.cpp" ]
>>>> [mac#tool.sip.bindings._pkdiagram]
>>>> sources = [ "unsafearea.cpp", "_pkdiagram.cpp", "_pkdiagram_mac.mm" ]
>>> Plenty of examples here...
>>> https://www.riverbankcomputing.com/static/Docs/pyqtdeploy/sysroot.html#the-pyqt-demo-sysroot
>>> Phil


More information about the PyQt mailing list