Petr Ferdus wrote: > > I can build static version of fossil for Windows with TCL suport based > on trunk version 946c3eb640 [1]. With minor tweaking in > "compat\tcl-8.6\generic\tclInterp.c" it uses init.tcl served from the same
> directory as where fossil.exe file resides. > Seems a bit drastic to me. You should also be able set the TCL_LIBRARY environment variable to get a similar effect. > > It is possible to execute this version of fossil as server[2] but for some > reason I cant run it as a Windows service. It fails with error: > "Error 1053: The service did not respond to the start or control request > in a timely fashion" > It might be crashing. Since I'm unable to replicate this issue here, I can only assume it's due to some issue with the "tclInterp.c" customizations. > > Could you suggest, what might block service execution? Last issue with win > service was caused by "--files-urlenc" option. > What might be still interfering due to TCL enablement? Tips how to overcome > this limitation would be appreciated. > You'll need to set the *SYSTEM* environment PATH variable to point to the directory containing the Tcl library -OR- place it in the same directory as the executable. Also, you'll need to be sure the service account has access (via ACLs) to the directory containing Fossil, Tcl, and the repositories, including all contained sub-directories. I've tested this here (using a Kit DLL in the Fossil binary directory) and it works just fine. -- Joe Mistachkin _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
