But it's running on BigSur 11.0.1 and successfully loaded my DB, downloaded public tag repository updates, and applied them. The resulting distributable needs to have the client.py copied alongside it along with the static and help directories. # Everything below this is typically managed by PyOxidizer and doesn't need Register_target("install", make_install, depends=, default=True) Register_target("resources", make_embedded_resources, depends=, default_build_script=True) Register_target("exe", make_exe, depends=) # Tell PyOxidizer about the build targets defined above. Python_config = dist.make_python_interpreter_config()Įxe.add_python_resources(exe.pip_install())Įxe.add_python_resources(exe.read_package_root( However, you can look at results of some prepared examples and try out almost all functions of HYDRUS GUI. The demo version does not allow you to run calculations and save data. Policy.resources_location = "filesystem-relative:library" Here you can download installation programs for HYDRUS demo versions. 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.Policy = dist.make_python_packaging_policy() 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. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |