Hi, Due to previously mentioned problems with loading DLLs from weird places, I had to resort to modifying my root.dynamicpath entry in the .rootrc file. The only example I could find was located in the tutorials section. I think the sample Windows NT entries in the .rootrc file are incorrect (at least, they didn't work for me). 1) The seperator is a ":" for file lists. Besides the fact that a ":" is a valid character in a NT filename, the path resolution is done by the routine _searchenv, which uses a ";" as the seperator (see documentation). So all the ":"s in there should be changed to a ";". 2) The macro expansion in the example .rootrc file are all things like "$ROOTSYS/bin" or something. Reading the Env class (BASE_Env.cxx) it seems like the required syntax is "$(ROOTSYS)/bin" for expansion. Indeed, this seems to work. I would guess that the UNIX lines in this example were wrong for the same reason. 3) I couldn't tell... is the "~/rootlib" file syntax (the ~ part, your home directory) recognized on windows? I would guess not, but perhaps translation happens someplace I didn't see. The ~ syntax is also used in this example file. I replaced the "~" with $(HOME) and things seemed to work just fine. BTW, the distrubution I used was the windows nt (w/out source code). It may well be that a default unix distribution comes with a different .rootrc file in the tutorial section? Cheers, Gordon. p.s. Windows NT 4.0, Service Pack 4.
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:26:21 MET