![]() ![]() 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. Save the deactivation file (usually DEACTH3D.LF) Send a copy of this file to us and also to your HYDRUS reseller, if you have bought HYDRUS from a reseller. However, here is a different build, using an older version of Please try extracting and running that on your desktop or similar. Open the HYDRUS License and Activation dialog (main menu -> help -> HYDRUS License and Activation) Press the Deactivate HYDRUS button. 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. If you are on 3.10.x, that's ok-run the 'advanced' setup later on and choose the newer OpenCV. This makes Python available to your Windows. During the install process, make sure it has something like 'Add Python to PATH' checked. Hmm, yeah, I did not have luck building different kinds of debug build for the client. First of all, you will need to install Python. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |