Generate moc_*cpp after sip-module --no-compile

[Patrick Stinson]

Oh, I get it. The command line option is added by pyqt-builder. Then you
are referring to running qmake on the .pro file. That does add entries to
the Makefiles to generate those files. Thanks

On Sun, Oct 13, 2024 at 11:05 PM Patrick Stinson <patrickkidd at gmail.com>
wrote:

> Do you mean --no-compile on sip-module? I have been running this though
> don't see a Makefile. I've been then running moc manually since the api is
> simple.
>
> On Mon, Sep 2, 2024 at 2:10 PM Phil Thompson <phil at riverbankcomputing.com>
> wrote:
>
>> On 02/09/2024 19:07, Patrick Stinson wrote:
>> > Sorry, brain fart. I meant sip-build not sip-module.
>> >
>> >> On Sep 2, 2024, at 9:57 AM, Patrick Stinson <patrickkidd at gmail.com>
>> >> wrote:
>> >>
>> >> Hi there,
>> >>
>> >>
>> >> I am trying to figure out the intended way to generate the moc_*.cpp
>> >> sources for my app’s custom PyQt/sip extension before running
>> >> pyqtdeploy-build. This is for an automated build pipeline on GitHub.
>> >>
>> >> "sip-module —no-compile” will generate the extension's non-moc .cpp
>> >> and .h files but it doesn’t generate the moc_*.cpp. I have all this
>> >> working by just running “sip-module” without “—no-compile,” but that
>> >> unnecessarily builds the extension which adds extra redundant run
>> >> time. All I want to do is generate the sources so they can be compiled
>> >> in the app’s actual compilation phase.
>> >>
>> >> What is the intended way to do this? Is it to manually run the moc exe
>> >> to generate the sources?
>> >>
>> >> Cheers,
>> >> -Patrick
>>
>> I assume you are using PyQt-builder so I would use --no-make and run
>> make separately with the targets that will run moc only - hopefully
>> qmake generates useful targets.
>>
>> Phil
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20241013/add3f5ec/attachment.htm>