Prev: Parser tools : "expected start <= end for range"
Next: Help fix my code: Problem in making folder contents backup then delete it
From: Ahmad on 29 Jul 2010 10:00 I tried freeWrap, and it seems to be excellent and easy to use. One problem I have is that I'm not using normal TCL (tclsh), I'm using CAD tool specifc tclsh having some built in custom API's for this tool. Hence, I need to make this script executable with something like: #!/ path/to/the/tool/bin/tool_tclsh It seems that freeWrap converts the script blindly to be executable by normal tclsh (available in $path). Can I get around this somehow? Thanks, Ahmad On Jul 28, 5:12 pm, DTM <gone2cani...(a)gmail.com> wrote: > On Jul 27, 3:37 pm, Ahmad <ahmad.abdulgh...(a)gmail.com> wrote: > > > Hi, > > > I have a tcl script that I need to ship to my customer encrypted as > > it's some propitiatory contents that I don't need him to see. > > > What are the best practice in encrypting Tcl script? > > > Thanks, > > Ahmad > > I believe that the freeWrap application can do what you want. FreeWrap > can turn your TCL script into an executable binary with your source > code encrypted. > > See the freeWrap home page at: http://freewrap.sourceforge.net/ > > Dennis
From: Ahmad on 29 Jul 2010 10:00 I tried freeWrap, and it seems to be excellent and easy to use. One problem I have is that I'm not using normal TCL (tclsh), I'm using CAD tool specifc tclsh having some built in custom API's for this tool. Hence, I need to make this script executable with something like: #!/ path/to/the/tool/bin/tool_tclsh It seems that freeWrap converts the script blindly to be executable by normal tclsh (available in $path). Can I get around this somehow? Thanks, Ahmad On Jul 28, 5:12 pm, DTM <gone2cani...(a)gmail.com> wrote: > On Jul 27, 3:37 pm, Ahmad <ahmad.abdulgh...(a)gmail.com> wrote: > > > Hi, > > > I have a tcl script that I need to ship to my customer encrypted as > > it's some propitiatory contents that I don't need him to see. > > > What are the best practice in encrypting Tcl script? > > > Thanks, > > Ahmad > > I believe that the freeWrap application can do what you want. FreeWrap > can turn your TCL script into an executable binary with your source > code encrypted. > > See the freeWrap home page at: http://freewrap.sourceforge.net/ > > Dennis
From: ZB on 1 Aug 2010 06:48
Dnia 28.07.2010 Ahmad <ahmad.abdulghany(a)gmail.com> napisa�/a: > Actually, what I meant is to keep the end-user unable to see the > contents of my tcl files. There is an obfuscator called Frink: http://catless.ncl.ac.uk/Programs/Frink/ But it seems to be abandoned, as it works only up to TCL 8.4.x -- Zbigniew |