01:13:36,638 5064 - Registering new command 'info' in assembly 'choco' 01:13:36,638 5064 - Registering new command 'list' in assembly 'choco' 01:13:36,638 5064 - Registering new command 'export' in assembly 'choco' 01:13:36,625 5064 - Registering new command 'upgrade' in assembly 'choco' 01:13:36,625 5064 - Registering new command 'templates' in assembly 'choco' 01:13:36,311 5064 - Adding new type 'SystemStateValidation' for type 'IValidation' from assembly 'choco' 01:13:36,311 5064 - Adding new type 'RubyGemsService' for type 'ISourceRunner' from assembly 'choco' 01:13:36,295 5064 - Adding new type 'PythonService' for type 'ISourceRunner' from assembly 'choco' 01:13:36,295 5064 - Adding new type 'CygwinService' for type 'ISourceRunner' from assembly 'choco' 01:13:36,295 5064 - Adding new type 'WindowsFeatureService' for type 'ISourceRunner' from assembly 'choco' 01:13:36,280 5064 - Adding new type 'WebPiService' for type 'ISourceRunner' from assembly 'choco' 01:13:36,123 5064 - XmlConfiguration is now operational HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Hydrus Network_is1 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.S-1-5-21-349732950-2472141918-6728823-1000 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. Two debug modes fail to build, and another appeared to go ok, but then does not boot the exe correctly. 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 |