WIndows Installer #370
Comments
|
I'll look into this soon... |
|
Installer still unavailable. You can compile from source code and run the program by following my toturial(3 exes to install and 10 commands from windows terminal): |
|
Just wanted to see if there's any work on this. It would help so many people to have an installer. |
|
would also like this, Make files isn't recognized by windows or VScode even with make installed, no other solutions seem to work. Considering most of us here are likely colorists or similar and not programmers it would be nice to have an installer for windows so updates aren't a day long process. |
…s for Python 3.10+ this returns the wrong value.
…to the usage of `sys.version` where it is replaced with `sys.version_info` as for Python 3.10+ this returns the wrong value.
|
Status update! I'm now able to generate the executables... but they don't run, probably related to a missing DLL... I'm on it.
|
|
Found the problem, microsoft wants a 4 part version number to be listed in the manifest, so adding a "0" to the version number (3.9.12.0 instead of 3.9.12) worked :) Now the executable starts 👍
Let's work on the installer... |
…version number to allow the embedded manifest to follow Microsoft rules and the frozen executable to run.
|
So the C:\Users\eoyil\AppData\Local\Temp\DisplayCAL-bu_gasc3>"C:\Users\eoyil\Documents\development\displaycal-py3\dist\py2exe.win-amd64-py3.11\DisplayCAL-3.9.12\lib\python.exe" -S -c "import sys; sys.path = ['C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12', 'C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12\\library.zip', 'C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12\\library.zip\\DisplayCAL', 'C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12\\lib\\library.zip', 'C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12\\lib\\library.zip\\DisplayCAL'] + sys.path;args = ['C:\\Users\\eoyil\\Downloads\\Argyll_V3.3.0\\bin\\dispread.exe', '-v', '-k', 'C:\\Users\\eoyil\\Documents\\development\\displaycal-py3\\dist\\py2exe.win-amd64-py3.11\\DisplayCAL-3.9.12\\linear.cal', '-d1', '-c1', '-yn', '-P0.49611307420494705,0.520863309352518,1.364864864864865', '0_16']; from DisplayCAL import wexpect;wexpect.ConsoleReader(wexpect.join_args(args), 11620, 2304, cp=1252, c=160, r=None, logdir='DisplayCAL')"
Could not find platform independent libraries <prefix>
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "DisplayCAL\wexpect.pyc", line 92, in <module>
File "pywintypes.pyc", line 126, in <module>
File "pywintypes.pyc", line 108, in __import_pywin32_system_module__
ImportError: No system module 'pywintypes' (pywintypes311.dll)I'm still trying to fix this... I saw one comment suggesting to use |
…layCAL.wxScriptingClient` for `bytes` vs `str` problems.
…tialize the `print_` arg with `None` and set its default value inside the method, instead of writing a complex expression on the argument itself.
…e returned by the `kernel32` library instead of manually setting it to `utf-8` as `cp1252` seems to be working fine, after #383 has been merged. And, simplified a couple of `if` statements that are checking the `stdout.isatty()` value, and updated code formatting.
|
I'm wrong So the real problem I suspect is again related with the codepage being |
|
No :) I'm wrong, that was the problem... Fixed, and the exe is working now... Let me run a complete calibration and profiling. |
…commands through `py2exe` frozen `python` interpretter.
|
Yeah, so it completed the profiling and installed the profile system wide without any errors. Now, let's create the installer. |
…s for Python 3.10+ this returns the wrong value.
…to the usage of `sys.version` where it is replaced with `sys.version_info` as for Python 3.10+ this returns the wrong value.
…version number to allow the embedded manifest to follow Microsoft rules and the frozen executable to run.
…layCAL.wxScriptingClient` for `bytes` vs `str` problems.
…tialize the `print_` arg with `None` and set its default value inside the method, instead of writing a complex expression on the argument itself.
…e returned by the `kernel32` library instead of manually setting it to `utf-8` as `cp1252` seems to be working fine, after #383 has been merged. And, simplified a couple of `if` statements that are checking the `stdout.isatty()` value, and updated code formatting.
…commands through `py2exe` frozen `python` interpretter.
… that the installer uses "Program Files" instead of "Program Files (x86)" by default.
…file path between quotes to prevent space characters in the file path to cause any errors.
…conf()` for a `str` vs `bytes` error raised when the VCGT doesn't have exactly 256 entries.
…gs under Windows and not under Linux/MacOS.
|
I'm inclained to merge this branch to #367 and release a new version all together. We now have a Windows Installer which this ticket is about, profiling and installing the profile is working. But we might have kinks that we need to fix with other tickets. |
|
Okay so, this is merged to #367 and the Windows Installer will be released with 3.9.13 soon. |
Any way to make a windows installer available?
The text was updated successfully, but these errors were encountered: