On 10/15/20 9:30 PM, Friedemann Kleint wrote:
>>I’d be satisfied if I could just find a programmatic way of injecting the
>>missing #includeat the beginning of the file.
>> Having to wait until my build breaks before intervening by manually editing
>> an auto-generated file feels all wrong.
>
Hi,
>I know that the usual outcome of these things involves writing a minimal
example that reproduces the problem.
> That would be challenging this case, since it’s a fairly L large library
written by someone else. But if the above offers any clues, then great.
Some information on the project
On 10/14/20 14:29 PM, Cristián Maureira-Fredes wrote:
>On 10/14/20 5:21 PM, Stephen Morris wrote:
>> On 10/14/20 12:45 PM, Cristián Maureira-Fredes wrote:
>>
>>> On 10/14/20 1:35 PM, Stephen Morris wrote:
>>>
On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:
>>
>>> >>On 10/12/20 1:
On 10/14/20 5:21 PM, Stephen Morris wrote:
On 10/14/20 12:45 PM, Cristián Maureira-Fredes wrote:
On 10/14/20 1:35 PM, Stephen Morris wrote:
On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:
On 10/12/20 1:14 PM, Stephen Morris wrote:
[snip]
Hello,
Can you try to use a newer libc
On 10/14/20 12:45 PM, Cristián Maureira-Fredes wrote:
>On 10/14/20 1:35 PM, Stephen Morris wrote:
>
>> On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:
>
>> On 10/12/20 1:14 PM, Stephen Morris wrote:
[snip]
>Hello,
>Can you try to use a newer libclang?
>There are some pre-built packages
On 10/14/20 1:35 PM, Stephen Morris wrote:
On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:
On 10/12/20 1:14 PM, Stephen Morris wrote:
Following an apparently successful build of Qt 5.15.1 and PySide2
5.15.1 from source, I'm now attempting to compile the application
which I was previo
On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:
>On 10/12/20 1:14 PM, Stephen Morris wrote:
>> Following an apparently successful build of Qt 5.15.1 and PySide2
>> 5.15.1 from source, I'm now attempting to compile the application
>> which I was previously compiling using version 5.12.5.
On 10/12/20 1:14 PM, Stephen Morris wrote:
Following an apparently successful build of Qt 5.15.1 and PySide2 5.15.1
from source, I'm now attempting to compile the application which I was
previously compiling using version 5.12.5.
I get a slew of error messages involving PySide Properties:
[
I found this documentation... (continued below)
https://doc.qt.io/qtforpython/shiboken2/typesystem_codeinjection.html
On 10/12/20 3:26 PM, Stephen Morris via PySide wrote:
OK, I got this to build with the aid of a filthy hack: I'd still appreciate
advice on how to avoid the hack...
On 10/12/20
OK, I got this to build with the aid of a filthy hack: I'd still appreciate
advice on how to avoid the hack...
On 10/12/20 1:11 PM, Stephen Morris via PySide wrote:
A further observation...
On 10/12/20 12:14 PM, Stephen Morris via PySide wrote:
Following an apparently successful build of Qt 5.
A further observation...
On 10/12/20 12:14 PM, Stephen Morris via PySide wrote:
Following an apparently successful build of Qt 5.15.1 and PySide2 5.15.1 from
source, I'm now attempting to compile the application which I was previously
compiling using version 5.12.5.
I get a slew of error messa
A further observation...
On 10/12/20 12:14 PM, Filippo Rusconi via PySide wrote:
Following an apparently successful build of Qt 5.15.1 and PySide2 5.15.1 from
source, I'm now attempting to compile the application which I was previously
compiling using version 5.12.5.
I get a slew of error mess
12 matches
Mail list logo
