This issue only effects the "installer" version of the program. If the program is run from source in windows the command line interface works fine.
It appears that it is not really possible to have the same executable work as both a command line program and a gui program (atleast not as the code is currently structured). Since the typical user will not need the CLI, I'm not too motivated to change things. If they do need it, they can always install from source.
If it is ever determined that it would be useful for a large number of windows users have a CLI option, my recommendation would be to create 2 separate executables (one for GUI and one for CLI). The gui one could be named something like ldscompactdirw.exe while the other remained ldscompactdir.exe. This would be simple enough to do with py2exe and inno setup.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This issue only effects the "installer" version of the program. If the program is run from source in windows the command line interface works fine.
It appears that it is not really possible to have the same executable work as both a command line program and a gui program (atleast not as the code is currently structured). Since the typical user will not need the CLI, I'm not too motivated to change things. If they do need it, they can always install from source.
If it is ever determined that it would be useful for a large number of windows users have a CLI option, my recommendation would be to create 2 separate executables (one for GUI and one for CLI). The gui one could be named something like ldscompactdirw.exe while the other remained ldscompactdir.exe. This would be simple enough to do with py2exe and inno setup.