search

MeVisLab / pythonqt

Dynamic Python binding for Qt Applications
https://mevislab.github.io/pythonqt/
GNU Lesser General Public License v2.1
251 stars 89 forks source link

[Solved] Cannot parse file: ':/trolltech/generator/build_all.txt' #202

Closed huskier closed 6 months ago

huskier commented 7 months ago

[Solved] The current master source code has some problem, and we have to get the 3.5.0 branch to compile successfully.

We've compiled PythonQt on Windows 11 platform, and the related information as following: Python: 3.11 (Anaconda Python distribution) Qt: 5.15.2 LTS Compiler tools: MSVC2019 (x64)

It seems that PythonQt is successfully compiled and linked. However, We still get the following error. We have no idea about the error. Any ideas about the error?

12:56:52: Starting D:\development\github_gitlib\build-PythonQt-Desktop_Qt_5_15_2_MSVC2019_64bit-Release\generator\release\pythonqt_generator.exe... ghijt LoadLibrary(C:\Program Files (x86)\Qianxin\Tianqing\hookbase\x64\VCOMP140.DLL) success Please wait while source files are being generated... Trying to determine Qt version...

Using QT at: C:\Application\Qt\5.15.2\msvc2019_64

Determined Qt version is 5.15.2 Parsing typesystem file [:/trolltech/generator/build_all.txt] Fatal error: line=1, column=1, message=unexpected end of file

Fatal error: line=2, column=62, message=Failed to parse: 'typesystem_core.xml'

Cannot parse file: ':/trolltech/generator/build_all.txt' 12:56:56: D:\development\github_gitlib\build-PythonQt-Desktop_Qt_5_15_2_MSVC2019_64bit-Release\generator\release\pythonqt_generator.exe crashed.

mrbean-bremen commented 7 months ago

So, what was the solution?

huskier commented 7 months ago

I don't know how to solve the issue directly, but I could workaround it through switching to 3.5.0 source code.

mrbean-bremen commented 7 months ago

Ok, so your problem was with the current master? In this case it could be a regression...

huskier commented 7 months ago

Maybe. Maybe it need more people to test this issue.

mrbean-bremen commented 7 months ago

So, did I understand you correctly, that the problem happenend with the current master, but not with the 3.5.0 release sources? Or did you use another version before?

huskier commented 7 months ago

Yes, you are right. There is no problem for 3.5.0 release source. The problem happend on the current master source.

Actually, I don't quite understand the timeline in the git commit log. The current master is leg after the v3.5.0 branch? image

mrbean-bremen commented 7 months ago

Thank you! The time line is related to the initial commit time, that happened before the release, but the commits have been merged only after the release.

mrbean-bremen commented 7 months ago

I checked all changes between master and the release tag, and couldn't find anything that even remotely could cause such a problem. All CI has been run successfully with current master, without any such warning, as far as I could see.

So my current assumption is that a typesystem file had been modified locally (maybe accidentally) that caused the problem, and that was reverted by the reset to 3.5.0.

@huskier - if this is possible, could you please check again by building against current master (making sure no other changes are made)?

mrbean-bremen commented 6 months ago

Closing as not reproducible. Feel free to reopen if you can reproduce the problem.