My end customer wants the script to be converted into a command(single executable binary) which can be executed directly from any location and his end user cannot see the exact code behind it.
On Mon, 7 Jan 2019, 03:56 Jon Szymaniak <jon.szymaniak.f...@gmail.com wrote: > Could you provide a bit more context about your particular use-case and > need to do this? > > i.e. Why is deployment of the existing script insufficient? > > I know this isn’t addressing your underlying question, but just want to > see if perhaps an alternative solution may be a better one for you. > > On Sun, Jan 6, 2019 at 13:12 nishant poorswani <nishantpoorsw...@gmail.com> > wrote: > >> Hi, I wanted to know which is the best way of converting a bash script >> into an executable binary in yocto. One way to do this is to add a recipe >> for shc( script compiler) in yocto and then use the shc for compiling it in >> another recipe. Is there any other way to achieve this ? Any suggestions >> would be deeply appreciated. >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
