Some questions about next versions of SIP

[Patrick Stinson]

I have always appreciated anything like a —jobs option. MAKEFLAGS sometimes works but isn’t always reliable for qt/pyqt5 builds, and it has sometimes been clear where to add a “-jN” option in the pyqtdeploy source code but only in a minority of cases and versions.

> On Sep 18, 2020, at 3:42 AM, Phil Thompson <phil at riverbankcomputing.com> wrote:
> 
> On 16/09/2020 10:04, Florian Bruhin wrote:
>> On Wed, Sep 16, 2020 at 09:31:27AM +0100, Phil Thompson wrote:
>>> On 16/09/2020 04:19, Kovid Goyal wrote:
>>> > On Tue, Sep 15, 2020 at 10:46:30PM +0530, Kovid Goyal wrote:
>>> > > Best I can come up with is to use sip-build and install manually
>>> > > myself
>>> >
>>> > That's what I ended up doing. Another question, how do I get sip-build
>>> > to use multiple CPU cores? With configure.py there was -j there doesnt
>>> > seem
>>> > to be any equivalent in sip-build. Makes building PyQt unnecessarily
>>> > slow.
>>> You can run sip-build with --no-make and run make separately. Or I can add
>>> an option. I'm happy to add options, features etc. to fix gaps in the
>>> current implementation.
>> FWIW I'd also appreciate to have an option to easily parallelize builds
>> without having to call make separately.
>> We're now at a point where it doesn't seem very exotic to have 12-16
>> cores in an affordable, portable 14" laptop[1], so IMHO it should be as
>> easy as possible to utilize those, as it does make things a lot faster.
>> Maybe it should even default to the number of available cores (i.e.
>> "nproc")? Though others might prefer using a single job by default like
>> make does as well, not sure.
> 
> I've added a --jobs option.
> 
> Phil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20200918/b2af6850/attachment.htm>