![]() Since you are comfortable with running from python source, did you happen to already have python or C++ Qt already on your system? I have had a couple reports before about system-wide Qt environment variables sometimes upsetting hydrus's private Qt. If this works for you, that narrows down the problem. ![]() Does it boot? Does it give you a different error? Different versions of pyinstaller work better or worse for certain unusual situations, such as running the program with a symlink. However, here is a different build, using an older version of Please try extracting and running that on your desktop or similar. There is supposed to now be a 'windowed' dialog hook to display the debug traceback, but I am only getting problems through it. I believe this is ultimately because of Qt wanting to be a non-console (windowed) program, and the debug normally working with console output. Double-click client.exe or tick the 'Launch client' checkbox on the install wizard. ![]() Environment Hydrus version: 400 OS: Windows 3.900 64-bit Steps to reproduce Extract or install version 400. Two debug modes fail to build, and another appeared to go ok, but then does not boot the exe correctly. Double-click client.exe or tick the 'Launch client' checkbox on the install wizard. Hmm, yeah, I did not have luck building different kinds of debug build for the client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |