Re: [Development] [EXTERNAL EMAIL] Could support for C be added to Qt?

2022-09-13 Thread samuel ammonius
Hi Mark, Thanks for clarifying it to me. I'll read the SWIG documentation and try to get it to work before trying anything else. I'll send a reply later to tell you if it worked or not. ___ Development mailing list Development@qt-project.org https://list

[Development] Meeting minutes from Qt Release Team meeting 13.09.2022

2022-09-13 Thread Jani Heikkinen
Qt 6.3 status: - Qt 6.3.2 released * will be he last release from Qt 6.3 series Qt 6.4 status: - Qt 6.4.0 RC preparations ongoing * RC content frozen and dependency update round ongoing * We will release Qt 6.4.0 RC Thu 15th September is nothing new found during package testing - Target

Re: [Development] qsizetype

2022-09-13 Thread Volker Hilsheimer
> On 12 Sep 2022, at 20:04, A. Pönitz wrote: > > On Wed, Sep 07, 2022 at 06:38:30PM +0200, A. Pönitz wrote: >> On Mon, Sep 05, 2022 at 05:15:45PM +, Marc Mutz wrote: >>> [...] >>> We have the tools (QT_REMOVED_SINCE + Ivan's work on >>> -disable-deprecated-until) to have a user-configurab

Re: [Development] [EXTERNAL EMAIL] Could support for C be added to Qt?

2022-09-13 Thread Mark De Wit
Hi Sam, I’m afraid you are misunderstanding SWIG. Swig generates language bindings from C and C++ code. It does this by creating a pure “C” wrapper for the code that is being wrapped. I.e. exactly the kind of thing you are proposing. After creating this export library, it then creates an im