<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Just running make was my first thought, but I don't see a Makefile (or equivalent for any other build system) anywhere. I only see the generated .cpp and .h files and the .o files in the build directory. Poking around the sip Python code, it seems like the
compilation and linking are orchestrated there. In theory I could roll my own Makefile, but that is unappealing, giving the number of compiler flags.
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Any other ideas? A different approach would be if there was a way to inject code into the sipAPIxxx.h file.<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
-ED<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Phil Thompson <phil@riverbankcomputing.com><br>
<b>Sent:</b> Thursday, November 16, 2023 11:53 PM<br>
<b>To:</b> Edward A. Pier <epier@oceanit.com><br>
<b>Cc:</b> pyqt@riverbankcomputing.com <pyqt@riverbankcomputing.com><br>
<b>Subject:</b> [External] Re: building code already generated by sip-build</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">[You don't often get email from phil@riverbankcomputing.com. Learn why this is important at
<a href="https://aka.ms/LearnAboutSenderIdentification">https://aka.ms/LearnAboutSenderIdentification</a> ]<br>
<br>
On 16/11/2023 14:12, Edward A. Pier wrote:<br>
> I am using sip to wrap some Qt-related C++ code in Python. I am<br>
> running sip-build 6.7.12 under MSYS2 on Windows.<br>
><br>
> The project compilation fails with a long spew of errors coming from<br>
> the qmetatype.h header file which is included by sipAPIxxx.h (I<br>
> substituted xxx for the project name).<br>
><br>
> The includes at the top of that file look like this:<br>
><br>
> #include "sip.h"<br>
><br>
> #include <QMetaType><br>
> #include <QThread><br>
><br>
> I find that if I swap the order of the QMetaType and QThread includes,<br>
> it compiles.<br>
><br>
> While it would be nice to understand and fix the ultimate cause of<br>
> this problem, I would settle for a workaround where I generate the<br>
> code, then modify the generated code, and then compile. I see there is<br>
> a --no-compile option on sip-build that would handle the first thing,<br>
> but I don't see a way to just compile already generated code with all<br>
> the necessary compiler flags.<br>
><br>
> Thanx for your help, and let me know if you need any more info.<br>
<br>
Just run make?<br>
<br>
Phil<br>
</div>
</span></font></div>
</body>
</html>