Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
My initial reason for wanting to do this was to move a bunch of scripts out of my home dir into a usr binary folder, and wouldn't feel good about myself unless they were legit binaries. Motivation = aesthetic, not functional. I suppose if this could be done well, though, it might also have some performance gains?
An application written in a compiled language--eg C--will, in principle, be faster than one written in an interpreted language (includes shell scripts). In practice, the difference will not always be significant.
Assuming that there is some utility that turns a shell script into a binary, I would expect it to be slower than either option above.
Wanting to make it a binary just so it can exist happily in /xxx/bin makes NO sense. The only reason for any executable file to exist is if it does something useful for you. Assuming that it does, then why would anyone care what was inside that file? (Or what directory it was in)
OTOH, if the script is too slow, warm up the C compiler and write something that does what you need.