I am frustrated of finding the executable in large list of bundled libraries and files. There are more than 40 files in the main directory of OneDir build. Exposing that directory to users might irritate them in finding the correct file to click, hence decreasing usability and effectiveness of software.
I also tried OneFile build, but facing ABI Incompatibility issues #5573
Solution:
A better way will be to shift dist/<onedir> to dist/newfolder/<onedir> and creating a symlink in newfolder to point to the executable in jungle of files. This way user opening the directory will be happy with executables, others may choose to dive deeper. If not by default, at least an option to do so will be better.
I am frustrated of finding the executable in large list of bundled libraries and files. There are more than 40 files in the main directory of OneDir build. Exposing that directory to users might irritate them in finding the correct file to click, hence decreasing usability and effectiveness of software.
I also tried OneFile build, but facing ABI Incompatibility issues #5573
Solution:
A better way will be to shift
dist/<onedir>todist/newfolder/<onedir>and creating a symlink innewfolderto point to the executable in jungle of files. This way user opening the directory will be happy with executables, others may choose to dive deeper. If not by default, at least an option to do so will be better.