The Hydrus server doesn't really work as most people envision a server working. The server is only really useful for a few specific cases which will not apply for the vast majority of users. The vast majority of features are contained in the client itself so if you're new to Hydrus, just use that. You don't need to use the server to use Hydrus. 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.The hydrus_server.exe/hydrus_server.py is the victim of many a misconception. 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 |